Measurement job creation and performance data reporting for advanced networks including network slicing

ABSTRACT

Various embodiments herein define a performance data and measurement job creation solutions for advanced networks including network slicing, based on a service-based framework. The embodiments allow different kinds of consumers to flexibly use performance management services and performance data services, to collect real-time performance data and/or periodical performance data.

CROSS-REFERENCE TO RELATED APPLICATION(S)

This application claims priority to U.S. patent application Ser. No.16/247,050, filed May 16, 2019, which claims the benefit of U.S.Provisional Patent Application No. 62/618,977, filed Jan. 18, 2018,which are hereby incorporated by reference herein in their entirety.

TECHNICAL FIELD

This application relates generally to wireless communication systems,and more specifically to measurement job creation and performance datareporting.

BACKGROUND

Wireless mobile communication technology uses various standards andprotocols to transmit data between a base station and a wireless mobiledevice. Wireless communication system standards and protocols caninclude the 3rd Generation Partnership Project (3GPP) long termevolution (LTE); the Institute of Electrical and Electronics Engineers(IEEE) 802.16 standard, which is commonly known to industry groups asworldwide interoperability for microwave access (WiMAX); and the IEEE802.11 standard for wireless local area networks (WLAN), which iscommonly known to industry groups as Wi-Fi; and the MulteFire standarddeveloped by MulteFire Alliance. In 3GPP radio access networks (RANs) inLTE systems, the base station can include a RAN Node such as a EvolvedUniversal Terrestrial Radio Access network (E-UTRAN) Node B (alsocommonly denoted as evolved Node B, enhanced Node B, eNodeB, or eNB)and/or Radio network Controller (RNC) in an E-UTRAN, which communicatewith a wireless communication device, known as user equipment (UE) andin MulteFire systems can include a MF-AP. In fifth generation (5G)wireless RANs, RAN Nodes can include a 5G Node, new radio (NR) node or gNode B (gNB).

RANs use a radio access technology (RAT) to communicate between the RANNode and UE. RANs can include global system for mobile communications(GSM), enhanced data rates for GSM evolution (EDGE) RAN (GERAN),Universal Terrestrial Radio Access network (UTRAN), and/or E-UTRAN,which provide access to communication services through a core network.Each of the RANs operates according to a specific 3GPP RAT. For example,the GERAN implements GSM and/or EDGE RAT, the UTRAN implements universalmobile telecommunication system (UMTS) RAT or other 3GPP RAT, and theE-UTRAN implements LTE RAT.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

To easily identify the discussion of any particular element or act, themost significant digit or digits in a reference number refer to thefigure number in which that element is first introduced.

FIG. 1 illustrates an example management reference architecture inaccordance with one embodiment.

FIG. 2 illustrates an example PM service framework in accordance withone embodiment.

FIG. 3 illustrates a method in accordance with one embodiment fornetwork function performance management services.

FIG. 4 illustrates a method in accordance with one embodiment for anetwork slice subnet instance (NSSI) measurement job control service (aspart of NSSI PM service).

FIG. 5 illustrates a method in accordance with one embodimentperformance management service for a network slice instance (NSI).

FIG. 6 illustrates a method for collecting network or sub-networkperformance data that are not specific to network slicing in accordancewith one embodiment.

FIG. 7 illustrates a system in accordance with one embodiment.

FIG. 8 illustrates a system in accordance with one embodiment.

FIG. 9 illustrates a device in accordance with one embodiment.

FIG. 10 illustrates an example interfaces in accordance with oneembodiment.

FIG. 11 illustrates a control plane in accordance with one embodiment.

FIG. 12 illustrates a user plane in accordance with one embodiment.

FIG. 13 illustrates a components in accordance with one embodiment.

FIG. 14 illustrates a system in accordance with one embodiment.

FIG. 15 illustrates a components in accordance with one embodiment.

DETAILED DESCRIPTION

A detailed description of systems and methods consistent withembodiments of the present disclosure is provided below. While severalembodiments are described, it should be understood that the disclosureis not limited to any one embodiment, but instead encompasses numerousalternatives, modifications, and equivalents. In addition, whilenumerous specific details are set forth in the following description inorder to provide a thorough understanding of the embodiments disclosedherein, some embodiments can be practiced without some or all of thesedetails. Moreover, for the purpose of clarity, certain technicalmaterial that is known in the related art has not been described indetail in order to avoid unnecessarily obscuring the disclosure.

Various embodiments herein may define a performance data and measurementjob creation solutions for 5G networks and network slicing, based on aservice based framework. The embodiments may allow different kinds ofconsumers to flexibly use the PM services and performance data services,to collect real-time performance data and/or periodical performancedata.

Conventional solutions use PM IRP for measurement job creation betweenIRP Manager and IRP Agent. However, the PM IRP works for the existingmanagement architecture, which is not a service based architecture. Theexisting PM functionality only supports periodical performance datacollection, but not support real-time performance data collection.Additionally, the existing PM functionality does not provide the centralperformance data service, which can flexibly consumed by any kinds ofapplications. Moreover, New Radio (NR) and NextGen (NG)-Radio Accessnetwork (RAN) performance data are different from legacy networks.

For 5G networks and network slicing, network management is evolvingtowards a service based architecture. FIG. 1 illustrates an examplemanagement reference architecture 100, which shows an operations system120 that supports management interfaces to other systems. The examplemanagement reference architecture 100 comprises an organization A 114and an organization B 116. By way of example, organization A 114 isshown to have one or more of an enterprise systems 102, a networkmanagement layer service (NMLS 104), a network manager (NM 106), adomain manager (DM 108), an element manager (EM 110), a network element(NE 112), a management interface (Itf-N 118, and an operations system120.

In the operations system 120, a number of functions are present. Asexamples, a network manager in the operations system 120 may include thefollowing functions/entities: management and orchestration of networkservices; on-line network support for 3GPP services; network planningincluding radio planning; network configuration management;Self-Organizing network (SON) Management and Orchestration; alarmcorrelation; network event correlation; network supervision; networkperformance monitoring; operator terminal; Licensed Shared Access (LSA)Controller (LC); and Integration Reference Point (IRP) Manager. Asexamples, the Domain/Element Management layer in the operations system120 may include the following functions/entities: network configurationmanagement; alarm correlation; network performance monitoring; SONManagement and Orchestration; operator terminal; and IRP Agent.

The operations system 120 may include management interfaces 1 betweenthe network elements (NEs) and the Element Manager (EM) of a single PLMNOrganization; management interfaces 2 between the Element Manager (EM)and the network Manager (NM) of a single PLMN Organization; managementinterfaces 3 between the network Managers and the Enterprise Systems ofa single PLMN Organization; management interfaces 4 between the networkManagers (NMs) of a single PLMN Organization; management interfaces 4 abetween the Domain Managers (DMs) of a single PLMN Organization;management interfaces 5 between Enterprise Systems & network Managers ofdifferent PLMN Organizations; management interfaces 5 a between theDomain Managers (DMs) of different PLMN Organizations; managementinterfaces 6 between network Elements (NEs); management interfaces 7between the network Management Layer Service (NMLS) and the networkManager (NM). IRPs may be implemented at interfaces 2, 3, 4, 5 and 7.Some of the management interfaces (e.g., Itf-N, Itf-P2P) may supportperformance management (PM) functionalities.

The existing performance measurement Integration Reference Point (IRP)works for the existing network management architecture. The existingnetwork management architecture is not a service based architecture, andtherefore does not fit to PM for 5G networks and network slicing. For 5Gnetworks and network slicing, real-time performance data and theperformance data service are to enable various applications (e.g., SON,Mobile Edge Computing (MEC), data analytics) to use the performancedata. Therefore, new mechanisms for measurement job creation andperformance data reporting should be defined.

The PM for 3GPP network functions (NFs) is not only used for managingthe 3GPP NFs, but also for supporting the PM of NSSI, NSI andnon-slice-specific network. The present disclosure provides use casesand requirements for creation of measurement jobs for 3GPP NF, NSSI, NSIand/or non-slice-specific network as part of PM services.

In order to collect the performance data (performance measurementsand/or assurance data) of 3GPP NF, the measurement job may need to becreated. The measurement job could be a periodical job to periodicallycollect the required performance data, or a real-time job to collect thereal-time performance data. The real-time performance data is useful,for example, when the 5G network needs to be adapted in real-time or inlow latency to support some 5G services (e.g., V2X, mission criticalcommunication, etc.).

The performance data of 3GPP NF is not only used for managing the 3GPPNFs, but also for supporting the PM of NSSI, NSI and non-slice-specificnetwork. Embodiments herein provide use cases and requirements onreporting of performance data of 3GPP NF, as part of NF performance dataservice. The performance data could be periodical performance data orreal-time performance data, reporting of both kinds of performance datamay need to be supported.

The PM for network slice SubNet is not only used for managing the NSSIs,but also for supporting the PM of NSI. Embodiments herein provide usecases and requirements on creation of measurement job for NSSI, as partof network slice SubNet PM service.

In order to collect the performance data (performance measurementsand/or assurance data) of NSSI, the measurement job may need to becreated. The measurement job could be a periodical job to periodicallycollect the required performance data, or a real-time job to collect thereal-time performance data. The real-time performance data is useful,for example, when the 5G network needs to be adapted in real-time or inlow latency to support some 5G services (e.g., V2X, mission criticalcommunication, etc.).

The performance data of 3GPP network (NSSI, NSI or non-slice-specificnetwork) is an aspect of 5G management. Embodiments herein provide usecases and requirements on reporting of performance data of 3GPP network,as part of network performance data service. The performance data couldbe periodical performance data or real-time performance data, reportingof both kinds of performance data may need to be supported.

The PM for network slice is an aspect of 5G management. Embodimentsherein provide use cases and requirements on creation of measurement jobfor NSI, as part of network slice PM service.

In order to collect the performance data (performance measurementsand/or assurance data) of NSI, the measurement job may need to becreated. The measurement job could be a periodical job to periodicallycollect the required performance data, or a real-time job to collect thereal-time performance data. The real-time performance data is useful,for example, when the 5G network needs to be adapted in real-time or inlow latency to support some 5G services (e.g., V2X, mission criticalcommunication, etc.).

The PM for non-slice-specific 3GPP network is an aspect of 5Gmanagement. Embodiments herein provide use cases and requirements oncreation of measurement job for non-slice-specific 3GPP network, as partof network PM service.

In order to collect the performance data (performance measurementsand/or assurance data) of non-slice-specific 3GPP network, themeasurement job may need to be created. The measurement job could be aperiodical job to periodically collect the required performance data, ora real-time job to collect the real-time performance data. The real-timeperformance data is useful, for example, when the 5G network needs to beadapted in real-time or in low latency to support some 5G services(e.g., V2X, mission critical communication, etc.).

FIG. 2 illustrates an example PM service framework 200 for 5G networksand network (NW) slicing in accordance with one embodiment. The examplePM service framework 200 comprises a network slice 202 including anetwork performance management function (NPMF 204), a network slicemanagement function (NSMF 206), and a network slice subnet managementfunction (NSSMF 208). The example PM service framework 200 also includesan NF PM function (NFPMF 210), a NW performance data repository 212(NWPDR), an NF performance data repository 214 (NFPDR), and an NF 216.The NPMF 204, which in certain embodiments may be a network managementfunction (NMF), provides a NW PM service and sends non-slice-specificnetwork performance data to the NW performance data repository 212. TheNSMF 206 provides NW slice PM service, sends NW slice performance datato the NW performance data repository 212, and receives NW slice subnetperformance data from the NW performance data repository 212. The NSSMF208 provides NW slice SubNet PM service to the NSMF 206 and sends NWslice subnet performance data to the NW performance data repository 212.In this example, the NW performance data repository 212 provides NWperformance data services. The 216 may be any NF that provides NF PMservices. In this example, the NF 216 sends NF performance data to theNF performance data repository 214. The NFPMF 210 provides NF PMservices and receives NF performance data from the NF performance datarepository 214. In certain embodiments, the NFPMF 210 may be a networkfunction management function (NFMF). In this example, the NF performancedata repository 214 provides NF performance data services.

The functions (e.g., NFPMF, NPMF, NSSMF, NSMF), repositories (e.g.,NFPDR, NWPDR), and/or services (e.g., NF PM service, NF performance dataservice, NW PM service, NW slice PM service, NW slice subnet PM service)in the example PM service framework 200 and the following embodimentsmay be named differently, as long as they provide functions, services,or data. For example, certain embodiments described herein may simplyrefer to the NPMF 204, NSMF 206, NSSMF 208, NFPMF 210, and/or NF 216 asa service producer or a particular type of service producer (e.g., NFmeasurement job control service producer, NSSI measurement job controlservice producer, an NSI measurement job control service producer, anetwork measurement job control service producer).

FIG. 2 also shows an authorized consumer 218. The authorized consumer218 may be any consumer of functions, data, or services. For example, asdescribed in certain embodiments herein, the NPMF 204, the NSMF 206, theNSSMF 208, or an operator may be referred to as a consumer or anauthorized consumer. As described in detail below, the service producermay enable the authorized consumer 218 to create a measurement job forcollecting the performance data of NF(s), to query an ongoing NFmeasurement job, to get a performance data file of 3GPP NF(s), toreceive a performance data stream of 3GPP NF(s), to create a measurementjob for collecting performance data of a network slice subnet instance(NSSI), to query one or more ongoing NSSI measurement job, to get aperformance data file of 3GPP NSSI(s), to receive a performance datastream of NSSI(s), to create a measurement job for collectingperformance data of a network slice instance (NSI), to query one or moreongoing NSI measurement job, to get a performance data file of 3GPPNSI(s), to receive a performance data stream of NSI(s), to create ameasurement job for collecting network/subnetwork performance data thatare not specific to network slicing, to query ongoing networkmeasurement jobs that are not specific to network slicing, to getnetwork/subnetwork performance data that are not specific to networkslicing, and/or to receive a stream of network/subnetwork performancedata that are not specific to network slicing. Further, certainembodiments described herein do not use the NW performance datarepository 212 and/or the NF performance data repository 214.

A. Performance Management for 3GPP NF

FIG. 3 is a flowchart illustrating a method 300 in accordance with oneembodiment for network function performance management services. Themethod 300 may be performed, for example, by a service producer, such asan NFMF, NPMF, NFPMF, 3GPP NF, or NF measurement job control serviceproducer. In block 302, the method 300 receives a measurement jobcreation request, from an authorized consumer, to create a measurementjob to collect performance data of one or more NF. In block 304, inresponse to the measurement job creation request, the method 300requests the one or more NF to collect the performance data. As shown inblock 306, wherein the measurement job creation request indicateswhether the performance data is to be reported by performance data fileor by performance data streaming.

An example embodiment of the method 300 is shown in Table 1.

TABLE 1 Use case stage Evolution/Specification Goal To enable theauthorized consumer (of NF PM service) to create a measurement job forcollecting the performance data (i.e., performance measurements and/orassurance data) of 3GPP NF. Actors and Roles An authorized consumer(e.g., NSSMF, NSMF, NMPF or an operator) of NF PM service. NFPMF or NFthat provides the NF PM service. Telecom resources 3GPP NF NFPDRAssumptions N/A Pre-conditions The 3GPP NF has been deployed. The NF PMservice producer (NFPMF or NF) is in operation. Begins when Theauthorized consumer needs to create measurement job for collecting theperformance data of 3GPP NF. Step 1 (M) The authorized consumer requeststhe NF PM service producer (i.e., NFPMF or 3GPP NF) to createmeasurement job to collect the performance data of 3GPP NF. The requestneeds to indicate that the measurement job is a periodical job or areal-time job. Step 2 (CM) In case the NF PM service producer is NFPMF,the NFPMF requests the 3GPP NF to create the measurement job to collectthe performance data, per the received measurement job creation request.Step 3 (M) 3GPP NF measures the networks and generates the performancedata, according to the information of the measurement job. Step 4 (M)3GPP NF reports the performance data to NFPDR, in the following way:periodically according to reporting period of the measurement job, ifthe measurement job is a periodical job; in real-time, if themeasurement job is a real-time job. Ends when All the steps identifiedabove are successfully completed. Exceptions One of the steps identifiedabove fails. Post-conditions The measurement job for 3GPP NF has beencreated. Traceability REQ-PM_NF-FUN-1 and REQ-PM_NF-FUN-2

In another example, the method 300 is to enable the authorized consumerto create a measurement job for collecting the performance data ofNF(s). The telecom resources include NF(s) and a producer of the NFmeasurement job control service (as part of NF PM service), wherein theNF(s) have been deployed and an NF measurement job control serviceproducer is in operation. The method 300 begins when the authorizedconsumer needs to create a measurement job for collecting theperformance data of NF(s). The authorized consumer requests the NFmeasurement job control service producer to create a measurement job tocollect the performance data of NF(s). The request indicates that theperformance data needs to be reported by performance data file (e.g.,periodically) or by performance data streaming (e.g., real-timereporting). The NF measurement job control service producer requests theNF(s) to collect the performance data, per the received measurement jobcreation request. In certain embodiments, after the method 300, themeasurement job for NF(s) has been created, and the NF measurement jobcontrol service producer generates the performance data for the NFmeasurement job.

An example embodiment for reporting of performance data of 3GPP NF isshown in Table 2.

TABLE 2 Use case stage Evolution/Specification Goal To enable theauthorized consumer (of NF performance data service) to get theperformance data (i.e., performance measurements and/or assurance data)of 3GPP NF. Actors and Roles An authorized consumer (e.g., NSSMF, NSMF,NMPF or an operator) of NF performance data service. NFPDR that providesthe NF performance data service. Telecom resources 3GPP NF AssumptionsN/A Pre-conditions The 3GPP NF has been deployed. The NF performancedata service producer (NFPDR) is in operation. Begins when Theauthorized consumer needs to get the performance data of 3GPP NF. Step 1(M) The authorized consumer requests the NFPDR to report the performancedata of 3GPP NF. The request needs to indicate that the performance datais periodical data or real-time data. Step 2 (M) NFPDR reports theperformance data of 3GPP NF to the authorized consumer, in the followingway: sending performance data file ready notification to the consumer(to allow the consumer to download the performance data file), if therequested performance data is periodical data; transmitting theperformance data streaming to the consumer, if the requested performancedata is real-time data. Ends when All the steps identified above aresuccessfully completed. Exceptions One of the steps identified abovefails. Post-conditions The performance data of 3GPP NF have beenreported. Traceability REQ-PD_NF-FUN-1, REQ-PD_NF-FUN-2, REQ-PD_NF-FUN-3and REQ-PD_NF-FUN-4

Certain embodiments also include enabling the authorized consumer toquery the ongoing NF measurement jobs (i.e. the NF measurement jobs thathave been created by the subject consumer and not terminated). If theauthorized consumer needs to query the ongoing NF measurement jobs, theauthorized consumer queries the information about the ongoing NFmeasurement jobs from the NF measurement job control service producer.The NF measurement job control service producer then provides theinformation about the ongoing NF measurement jobs to the consumer.

Certain embodiments also include enabling the authorized consumer to getthe performance data file of 3GPP NF(s). When a performance data file ofthe 3GPP NF is ready at a NF performance data file reporting serviceproducer, the NF performance data file reporting service producer sendsa notification about performance data file ready to the authorizedconsumer. The authorized consumer then fetches the performance data filefrom the NF performance data file reporting service producer.

Certain embodiments also include enabling the authorized consumer toreceive the performance data stream of 3GPP NF(s). When the performancedata of the 3GPP NF is ready at the NF performance data streamingservice producer, an NF performance data streaming service producersends the NF performance data stream to the consumer.

B. Performance Management for NSSI

FIG. 4 is a flowchart in accordance with one embodiment illustrating anNSSI measurement job control service (as part of NSSI PM service). Themethod 400 may be performed by, for example, a service producerconfigured to provide a performance management service for NSSI, such asan NFPMF, 3GPP NF, or an NSSI measurement job control service producer.In block 402, the method 400 receives a request to create an NSSImeasurement job to collect performance data of one or more NSSI. Inblock 404, the method 400 decomposes the performance data of the one ormore NSSI into performance data types of constituent NSSIs and/ornetwork functions (NFs). In block 406, the method 400 determines whetherthe performance data types of the constituent NSSI(s) and/or NFs can becollected by existing measurement jobs, if any, for the constituentNSSI(s) and/or NFs. In block 408, in response to determining that theperformance data types cannot be collected by the existing measurementjobs for the constituent NSSI(s) and/or NFs, the method 400 creates oneor more new measurement jobs for the constituent NSSI(s) and/or NFs,respectively.

An example of the method 400 is shown in Table 3.

TABLE 3 Use case stage Evolution/Specification Goal To enable theauthorized consumer (of Network Slice SubNet PM service) to create ameasurement job for collecting the performance data (i.e., performancemeasurements and/or assurance data) of NSSI. Actors and Roles Anauthorized consumer (e.g., NSMF or an operator) of Network Slice SubNetPM service. NSSMF that provides the Network Slice SubNet PM service.Telecom resources NSSI NF PM service producer (NFPMF or NF) NFperformance data service producer (NFPDR) 3GPP NF Assumptions N/APre-conditions The NSSI has been deployed The Network Slice SubNet PMservice producer (i.e., NSSMF) is in operation. Begins when Theauthorized consumer needs to create measurement job for collecting theperformance data of NSSI. Step 1 (M) The authorized consumer requeststhe NSSMF to create measurement job to collect the performance data ofNSSI. The request needs to indicate that the measurement job is aperiodical job or a real-time job. Step 2 (M) The NSSMF decomposes theperformance data of NSSI into performance data of the constituent 3GPPNF(s). The NSSMF checks whether the decomposed performance data of theconstituent 3GPP NF(s) can be collected by the existing measurementjob(s) for 3GPP NF(s). If new measurement job(s) for the constituent3GPP NF(s) are required, NSSMF requests the NF PM service producer tocreate the new measurement job(s) for the constituent 3GPP NF(s)(according to the use case “Creation of measurement job for 3GPP NF” asdescribed in Table 1). Step 3 (M) NSSMF gets the performance data of theconstituent NF(s) from NFPDR (according to the use case “Reporting ofperformance data of 3GPP NF” as described in Table 2), and generate theperformance data of NSSI. Step 4 (M) NSSMF reports the performance dataof NSSI to NWPDR, in the following way: periodically according toreporting period of the measurement job for the NSSI, if the measurementjob is a periodical job; in real-time, if the measurement job for theNSSI is a real-time job Ends when All the steps identified above aresuccessfully completed. Exceptions One of the steps identified abovefails. Post-conditions The measurement job for NSSI has been created.Traceability REQ-PM_NSSI-FUN-1, REQ-PM_NSSI-FUN-2, REQ-PM_NSSI-FUN-3 andREQ-PM_NSSI-FUN-4

In another example, the method 400 is to enable the authorized consumerto create a measurement job for collecting the performance data ofNSSI(s). Telecom resources used for the 400 may include NSSI(s), an NSSImeasurement job control service producer, an NF measurement job controlservice producer, an NF performance data file reporting service producerand/or NF performance data streaming service producer, and an NSSIperformance data file reporting service producer and/or NSSI performancedata streaming service producer. When the authorized consumer needs tocreate measurement job for collecting the performance data of NSSI(s),the authorized consumer requests the NSSI measurement job controlservice producer to create an NSSI measurement job to collect theperformance data of NSSI(s). The request indicates that the performancedata is to be reported by a performance data file (e.g., periodically)or by performance data streaming (e.g., real-time).

In response, the NSSI measurement job control service producerdecomposes the performance data type(s) of NSSI into performance datatype(s) of the constituent NSSI(s) and/or NF(s). The NSSI measurementjob control service producer checks whether the decomposed performancedata types of the constituent NSSI(s) and NF(s) can be collected by theexisting measurement job(s) for NSSI(s) and/or NF(s). If new measurementjob(s) for the constituent NSSI(s) and/or NF(s) are required, the NSSImeasurement job control service producer consumes the NSSI measurementjob control service and/or the NF measurement job control service tocreate the new measurement job(s) for the constituent NSSI(s) and/orNF(s), respectively (e.g., according to the example use case discussedwith respect to FIG. 3). Once the measurement job for NSSI has beencreated, the NSSI measurement job control service producer may consumethe NSSI performance data file reporting service and/or NSSI performancedata streaming service to get the performance data of the constituentNSSI(s), and/or consume the NF performance data file reporting serviceand/or NF performance data streaming service to get the performance dataof the constituent NF(s), and generate the performance data for the NSSImeasurement job.

Table 4 shows example NSSI reporting of performance data of a 3GPPnetwork.

TABLE 4 Use case stage Evolution/Specification Goal To enable theauthorized consumer (of Network performance data service) to get theperformance data (i.e., performance measurements and/or assurance data)of 3GPP network, which could be NSSI, NSI or a non-slice-specificnetwork. Actors and Roles An authorized consumer (e.g., NSMF or anoperator) of Network performance data service. NWPDR that provides theNetwork performance data service. Telecom resources 3GPP network (NSI,NSSI or non-slice-specific network) Assumptions N/A Pre-conditions The3GPP network, whose performance data are to be reported, has beendeployed. The Network performance data service producer (NWPDR) is inoperation. Begins when The authorized consumer needs to get theperformance data of 3GPP network. Step 1 (M) The authorized consumerrequests the NWPDR to report the performance data of the 3GPP network.The request needs to indicate that the performance data is periodicaldata or real-time data. Step 2 (M) NWPDR reports the performance data of3GPP network to the authorized consumer, in the following way: sendingperformance data file ready notification to the consumer (to allow theconsumer to download the performance data file), if the requestedperformance data is periodical data; transmitting the performance datastreaming to the consumer, if the requested performance data isreal-time data. Ends when All the steps identified above aresuccessfully completed. Exceptions One of the steps identified abovefails. Post-conditions The performance data of 3GPP network have beenreported. Traceability REQ-PD_NW-FUN-1, REQ-PD_NW-FUN-2, REQ-PD_NW-FUN-3and REQ-PD_NW-FUN-4

Certain embodiments also include enabling the authorized consumer toquery the ongoing NSSI measurement jobs (i.e. the NSSI measurement jobsthat have been created by the subject consumer and not terminated). Whenthe authorized consumer needs to query the ongoing NSSI measurementjobs, the authorized consumer queries the information about the ongoingNSSI measurement jobs from the NSSI measurement job control serviceproducer. In response, the NSSI measurement job control service producerprovides the information about the ongoing NSSI measurement jobs to theconsumer.

Certain embodiments also include enabling the authorized consumer to getthe performance data file of 3GPP NSSI(s). When a performance data fileof 3GPP NSSI(s) is ready at the NSSI performance data file reportingservice producer, the NSSI performance data file reporting serviceproducer sends the notification about performance data file ready to theauthorized consumer. Then, the authorized consumer fetches theperformance data file from the NSSI performance data file reportingservice producer.

Certain embodiments also include enabling the authorized consumer toreceive the performance data stream of NSSI(s). When performance data of3GPP NSSI is ready at an NSSI performance data streaming serviceproducer, the NSSI performance data streaming service producer sends theNSSI performance data stream to the consumer.

C. Performance Management for NSI

FIG. 5 is a flowchart illustrating a method 500 in accordance with oneembodiment performance management service for a network slice instance(NSI). The method 500 may be performed by a service producer such as anNSMF or a producer of NSI measurement job control service (as part ofNSI PM service). In block 502, the method 500 receives a request, froman authorized consumer, to create a network slice instance (NSI)measurement job to collect performance data of one or more NSI, whereinthe request indicates whether the performance data is to be reported byperformance data file or by performance data streaming. In block 504,the method 500 decomposes the performance data of the one or more NSIinto performance data types of constituent network slice subnetinstances (NSSIs) and/or constituent network functions (NFs). In block506, the method 500 creates a new measurement job for at least one ofthe constituent NSSI(s) or the constituent NF(s).

Creating the new measurement job may include determining whetherdecomposed performance data of the constituent NSSI(s) can be collectedby existing measurement job(s) for NSSI(s). In response to determiningthat the decomposed performance data of the constituent NSSI(s) cannotbe collected by the existing measurement job(s) for NSSI(s), the method500 may also include creating the new measurement job for theconstituent NSSI(s).

In addition, or in other embodiments, creating the new measurement jobincludes determining whether decomposed performance data of theconstituent NF(s) can be collected by existing measurement job(s) forNF(s). In response to determining that the decomposed performance dataof the constituent NF(s) cannot be collected by the existing measurementjob(s) for NF(s), the method 500 includes requesting an NF PM serviceproducer to create the new measurement job for the constituent NF(s).

An example of the method 500 is shown in Table 5.

TABLE 5 Use case stage Evolution/Specification Goal To enable theauthorized consumer (of Network Slice PM service) to create ameasurement job for collecting the performance data (i.e., performancemeasurements and/or assurance data) of NSI. Actors and Roles Anauthorized consumer (e.g., an operator) of Network Slice PM service.NSMF that provides the Network Slice PM service. Telecom resources NSINSSI Network Slice SubNet PM service producer (NSMF) Network performancedata service producer (NWPDR) NF PM service producer (NFPMF or NF) NFperformance data service producer (NFPDR) Assumptions N/A Pre-conditionsThe NSI has been deployed. The Network Slice PM service producer (i.e.,NSMF) is in operation. Begins when The authorized consumer needs tocreate measurement job for collecting the performance data of NSI. Step1 (M) The authorized consumer requests the NSMF to create measurementjob to collect the performance data of NSI. The request needs toindicate that the measurement job is a periodical job or a real-timejob. Step 2 (M) The NSMF decomposes the performance data of NSSI intoperformance data of the constituent NSSI(s) and/or of constituent 3GPPNF(s). The NSMF checks whether the decomposed performance data of theconstituent NSSI(s) can be collected by the existing measurement job(s)for NSSI(s). If new measurement job(s) for the constituent NSSI(s) arerequired, NSSMF requests the Network Slice SubNet PM service producer tocreate the new measurement job(s) for the constituent NSSI(s) (accordingto the use case “Creation of measurement job for 3GPP NF” as describedin clause 5.1.2.x). The NSMF checks whether the decomposed performancedata of the constituent 3GPP NF(s) can be collected by the existingmeasurement job(s) for 3GPP NF(s). If new measurement job(s) for theconstituent 3GPP NF(s) are required, NSSMF requests the NF PM serviceproducer to create the new measurement job(s) for the constituent 3GPPNF(s) (according to the use case “Creation of measurement job for 3GPPNF” as described in Table 1). Step 3 (M) NSMF gets the performance dataof the constituent NSSI(s) from NWPDR (according to the use case“Reporting of performance data of 3GPP network” as described in clause5.1.y.1). If the performance data decomposition in Step 2 contains theperformance data of constituent 3GPP NFs, NSMF gets the performance dataof the constituent 3GPP NF(s) from NFPDR (according to the use case“Reporting of performance data of 3GPP NF” as described in Table 2).NSMF generates the performance data of NSI based on the obtainedperformance data of constituent NSSI(s) and/or of constituent 3GPPNF(s). Step 4 (M) NSMF reports the performance data of NSI to NWPDR, inthe following way: periodically according to reporting period of themeasurement job for the NSI, if the measurement job is a periodical job;in real-time, if the measurement job for the NSI is a real-time job.Ends when All the steps identified above are successfully completed.Exceptions One of the steps identified above fails. Post-conditions Themeasurement job for NSI has been created. Traceability REQ-PM_NSI-FUN-1,REQ-PM_NSI-FUN-2, REQ-PM_NSI-FUN-3 and REQ-PM_NSI-FUN-4

In another example, the method 500 enables the authorized consumer tocreate a measurement job for collecting the performance data of NSI(s).Telecom resources may include NSI(s), a set of an NSI measurement jobcontrol service producer, an NSSI performance data file reportingservice producer and/or NSSI performance data streaming serviceproducer, and/or a set of the NF measurement job control serviceproducer, NF performance data file reporting service producer and/or NFperformance data streaming service producer. When the authorizedconsumer needs to create measurement job for collecting the performancedata of NSI(s), the authorized consumer requests the NSI measurement jobcontrol service producer to create an NSI measurement job to collect theperformance data of NSI(s). The request indicates that the performancedata is to be reported by performance data file or by performance datastreaming. In response, the NSI measurement job control service producerdecomposes the performance data type of NSI(s) into performance datatype(s) of the constituent NSSI(s) and/or of constituent NF(s).

The NSI measurement job control service producer checks whether thedecomposed performance data of the constituent NSSI(s) can be collectedby the existing measurement job(s) for NSSI(s). If new measurementjob(s) for the constituent NSSI(s) are required, the NSI measurement jobcontrol service producer consumes the NSSI measurement job controlservice to create the new measurement job(s) for the constituent NSSI(s)(e.g., according to the example use case discussed with respect to FIG.4). In addition or in other embodiments, the NSI measurement job controlservice producer checks whether the decomposed performance data of theconstituent NF(s) can be collected by the existing measurement job(s)for NF(s). If new measurement job(s) for the constituent NF(s) arerequired, NSI measurement job control service producer requests the NFPM measurement job control service producer to create the newmeasurement job(s) for the constituent NF(s) (e.g., according to theexample use case discussed with respect to FIG. 3).

When the measurement job for NSI has been created, the NSI measurementjob control service producer may consume the NSSI performance data filereporting service, the NSSI performance data streaming service, the NFperformance data file reporting service and/or NF performance datastreaming service to get the performance data of the constituent NSSI(s)and/or NF(s), and generates the performance data for the NSI measurementjob.

Certain embodiments also include enabling the authorized consumer toquery the ongoing NSI measurement jobs (i.e. the NSI measurement jobsthat have been created by the subject consumer and not terminated). Whenthe authorized consumer needs to query the ongoing NSI measurement jobs,the authorized consumer queries the information about the ongoing NSImeasurement jobs from the NSI measurement job control service producer.In response, the NSI measurement job control service producer providesthe information about the ongoing NSI measurement jobs to the consumer.

Certain embodiments also include enabling the authorized consumer to getthe performance data file of 3GPP NSI(s). When the performance data fileof 3GPP NSI(s) is ready at the NSI performance data file reportingservice producer, the NSI performance data file reporting serviceproducer sends the notification about performance data file ready to theauthorized consumer. In response, the authorized consumer fetches theperformance data file from the NSI performance data file reportingservice producer.

Certain embodiments also include enabling the authorized consumer toreceive the performance data stream of NSI(s). When the performance dataof 3GPP NSI is ready at the NSI performance data streaming serviceproducer, the NSI performance data streaming service producer sends theNSI performance data stream to the consumer.

D. Performance Management for Non-Slice-Specific 3GPP Network

FIG. 6 is a flowchart illustrating a method 600 for collecting networkor sub-network performance data that are not specific to network slicingin accordance with one embodiment. The method 500 may be performed by aservice producer such as an NPMF or a producer of network measurementjob control service (as part of network PM service). In block 602, themethod 600 receives a request, from an authorized consumer, to create ameasurement job for collecting non-slice-specific network performancedata, wherein the request indicates whether the performance data is tobe reported by performance data file or by performance data streaming.In block 604, the method 600 decomposes the non-slice-specific networkperformance data into performance data types of constituent networkfunctions (NFs). In block 606, the method 600 determines whether theperformance data types of the constituent NF(s) can be collected byexisting measurement jobs for NF(s). In block 608, the method 600requests to create one or more new measurement job for the constituentNF(s).

An example of the method 600 is shown in Table 6.

TABLE 6 Use case stage Evolution/Specification Goal To enable theauthorized consumer (of Network PM service) to create a measurement jobfor collecting the performance data (i.e., performance measurementsand/or assurance data) of non-slice-specific 3GPP network. Actors andRoles An authorized consumer (e.g., an operator) of Network PM service.NPMF that provides the Network PM service. Telecom resourcesNon-slice-specific 3GPP network Network performance data serviceproducer (NWPDR) NF PM service producer (NFPMF or NF) NF performancedata service producer (NFPDR) Assumptions N/A Pre-conditions Thenon-slice-specific 3GPP network has been deployed. The Network PMservice producer (i.e., NPMF) is in operation. Begins when Theauthorized consumer needs to create measurement job for collecting theperformance data of non-slice-specific 3GPP network . Step 1 (M) Theauthorized consumer requests the NPMF to create measurement job tocollect the performance data of non-slice-specific 3GPP network. Therequest needs to indicate that the measurement job is a periodical jobor a real-time job. Step 2 (M) The NPMF decomposes the performance dataof non-slice-specific 3GPP network into performance data of theconstituent 3GPP NF(s). The NPMF checks whether the decomposedperformance data of the constituent 3GPP NF(s) can be collected by theexisting measurement job(s) for 3GPP NF(s). If new measurement job(s)for the constituent 3GPP NF(s) are required, NPMF requests the NF PMservice producer to create the new measurement job(s) for theconstituent 3GPP NF(s) (according to the use case “Creation ofmeasurement job for 3GPP NF” as described in Table 1). Step 3 (M) NPMFgets the performance data of the constituent NF(s) from NFPDR (accordingto the use case “Reporting of performance data of 3GPP NF” as describedin Table 2), and generate the performance data of non-slice-specific3GPP network. Step 4 (M) NPMF reports the performance data ofnon-slice-specific 3GPP network to NWPDR, in the following way:periodically according to reporting period of the measurement job forthe non-slice- specific 3GPP network, if the measurement job is aperiodical job; in real-time, if the measurement job for thenon-slice-specific 3GPP network is a real-time job. Ends when All thesteps identified above are successfully completed. Exceptions One of thesteps identified above fails. Post-conditions The measurement job fornon-slice-specific 3GPP network has been created. TraceabilityREQ-PM_NW-FUN-1, REQ-PM_NW-FUN-2, REQ-PM_NW-FUN-3 and REQ-PM_NW-FUN-4

In another example, the method 600 enables the authorized consumer tocreate a measurement job for collecting the network/sub-networkperformance data that are not specific to network slicing. The telecomresources may be network(s)/sub-network(s), a network measurement jobcontrol service producer, an

NF measurement job control service producer, an NF performance data filereporting service producer, and/or an NF performance data streamingservice producer. When the authorized consumer needs to create a networkmeasurement job for collecting the network performance data that are notspecific to network slicing, the authorized consumer requests thenetwork measurement job control service producer to create measurementjob to collect the network performance data that are not specific tonetwork slicing.

The request indicates that the performance data are to be reported byperformance data file or by performance data streaming. In response, thenetwork measurement job control service producer decomposes theperformance data type of network/sub-network into performance datatype(s) of the constituent 3GPP NF(s). The network measurement jobcontrol service producer determines whether the decomposed performancedata type(s) of the constituent NF(s) can be collected by the existingmeasurement job(s) for NF(s). If new measurement job(s) for theconstituent NF(s) are required, the network measurement job controlservice producer requests the NF measurement job control serviceproducer to create the new measurement job(s) for the constituent NF(s)(e.g., according to the use case described in relation to FIG. 3). Incertain embodiments, once the measurement job fornetwork(s)/sub-network(s) has been created, the network measurement jobcontrol service producer consumes the NF performance data file reportingservice and/or NF performance data streaming service to get theperformance data of the constituent NF(s), and generates the performancedata for the network measurement job.

Certain embodiments also enable the authorized consumer to query theongoing network measurement jobs (i.e., the network measurement jobsthat have been created by the subject consumer and not terminated). Whenthe authorized consumer needs to query the ongoing network measurementjobs, the authorized consumer queries the information about the ongoingnetwork measurement jobs from the network measurement job controlservice producer. In response, the network measurement job controlservice producer provides the information about the ongoing networkmeasurement jobs to the consumer.

Certain embodiments also enable the authorized consumer to get thenetwork/sub-network performance data that are not specific to networkslicing. When the performance data file of network/sub-network is readyat the network/sub-network performance data file reporting serviceproducer, the network/sub-network performance data file reportingservice producer sends the notification about performance data fileready to the authorized consumer. The authorized consumer then fetchesthe network/sub-network performance data file from thenetwork/sub-network performance data file reporting service producer.

Certain embodiments also enable the authorized consumer to receive thestream of the network/sub-network performance data that are not specificto network slicing. When the performance data of network is ready at thenetwork/sub-network performance data streaming service producer, thenetwork/sub-network performance data streaming service producer sendsthe network/sub-network performance data stream to the consumer.

E. Example Requirements

The following are some example requirements for certain embodimentsherein. See, for example, the “Traceability” sections of Tables 1-6.

E(1) Requirements for NF PM Service

REQ-PM_NF-FUN-1: The NF PM service producer (i.e., NFPMF or 3GPP NF) hasthe capability allowing its authorized consumer to create a periodicalmeasurement job to collect the performance data of 3GPP NF.

REQ-PM_NF-FUN-2: The NF PM service producer (i.e., NFPMF or 3GPP NF) hasthe capability allowing its authorized consumer to create a real-timemeasurement job to collect the performance data of 3GPP NF.

E(2) Requirements for NF Performance Data Service

REQ-PD_NF-FUN-1: The NF performance data service producer (i.e., NFPDR)has the capability allowing its authorized consumer to get theperiodical performance data of 3GPP NF.

REQ-PD_NF-FUN-2: The NF performance data service producer (i.e., NFPDR)has the capability allowing its authorized consumer to get the real-timeperformance data of 3GPP NF.

REQ-PD_NF-FUN-3: The NF performance data service producer (i.e., NFPDR)has the capability to send the performance data file ready notification(for the periodical performance data of 3GPP NF) to its authorizedconsumer.

REQ-PD_NF-FUN-4: The NF performance data service producer (i.e., NFPDR)has the capability to transmit the performance data streaming (for thereal-time performance data of 3GPP NF) to its authorized consumer.

E(3) Requirements for Network Slice SubNet PM Service

REQ-PM_NSSI-FUN-1: The network slice SubNet PM service producer (i.e.,NSSMF) has the capability allowing its authorized consumer to create aperiodical measurement job to collect the performance data of NSSI.

REQ-PM_NSSI-FUN-2: The network slice SubNet PM service producer (i.e.,NSSMF) has the capability allowing its authorized consumer to create areal-time measurement job to collect the performance data of NSSI.

REQ-PM_NSSI-FUN-3: The network slice SubNet PM service producer (i.e.,NSSMF) has the capability to report the periodical performance data ofNSSI to NWPDR.

REQ-PM_NSSI-FUN-4: The network slice SubNet PM service producer (i.e.,NSSMF) has the capability to report the real-time performance data ofNSSI to NWPDR.

E(4) Requirements for Network Performance Data Service.

REQ-PD_NW-FUN-1: The network performance data service producer (i.e.,NWPDR) has the capability allowing its authorized consumer to get theperiodical performance data of 3GPP network (i.e., NSSI, NSI ornon-slice specific 3GPP network).

REQ-PD_NW-FUN-2: The network performance data service producer (i.e.,NWPDR) has the capability allowing its authorized consumer to get thereal-time performance data of 3GPP network (i.e., NSSI, NSI or non-slicespecific 3GPP network).

REQ-PD_NW-FUN-3: The network performance data service producer (i.e.,NWPDR) has the capability to send the performance data file readynotification (for the periodical performance data of 3GPP network) toits authorized consumer.

REQ-PD_NW-FUN-4: The network performance data service producer (i.e.,NWPDR) has the capability to transmit the performance data streaming(for the real-time performance data of 3GPP network) to its authorizedconsumer.

E(5′ Requirements for Network Slice PM Service

REQ-PM_NSI-FUN-1: The network slice PM service producer (i.e., NSMF) hasthe capability allowing its authorized consumer to create a periodicalmeasurement job to collect the performance data of NSI.

REQ-PM_NSI-FUN-2: The network slice PM service producer (i.e., NSMF) hasthe capability allowing its authorized consumer to create a real-timemeasurement job to collect the performance data of NSI.

REQ-PM_NSI-FUN-3: The network slice PM service producer (i.e., NSMF) hasthe capability to report the periodical performance data of NSI toNWPDR.

REQ-PM_NSI-FUN-4: The network slice PM service producer (i.e., NSMF) hasthe capability to report the real-time performance data of NSI to NWPDR.

E(6) Requirements for Network PM Service

REQ-PM_NW-FUN-1: The network PM service producer (i.e., NPMF) has thecapability allowing its authorized consumer to create a periodicalmeasurement job to collect the performance data of non-slice-specific3GPP network.

REQ-PM_NW-FUN-2: The network PM service producer (i.e., NPMF) has thecapability allowing its authorized consumer to create a real-timemeasurement job to collect the performance data of non-slice-specific3GPP network.

REQ-PM_NW-FUN-3: The network PM service producer (i.e., NPMF) has thecapability to report the periodical performance data ofnon-slice-specific 3GPP network to NWPDR.

REQ-PM_NW-FUN-4: The network PM service producer (i.e., NPMF) has thecapability to report the real-time performance data ofnon-slice-specific 3GPP network to NWPDR.

F. Example Use Case on Monitoring of RRC Connection Establishment

Radio resource control (RRC) connection establishment is a usefulprocedure in NR and NG-RAN. Without an RRC connection established, theUE generally cannot connect to NR or NG-RAN. The performance (e.g.,success rate) of RRC connection establishment has direct impact to theend user experience. When the NR or NG-RAN supports the network slicing,the gNB may support multiple NSIs and each NSI may be used to supportsome specific communication service, therefore each NSI may have its ownpriority in radio resource management. So, in certain embodiments, theRRC connection establishment may need to be monitored per NSI that thegNB supports. The performance measurements related to RRC connectionestablishment are useful for evaluation, optimization and performanceassurance of the network (including NSI, NSSI or non-slice-specificnetwork).

The following examples are directed to RRC connection relatedmeasurements for RRC connection establishment.

F(1) Attempted RRC Connection Establishments

a) This measurement provides the number of RRC connection establishmentattempts. This measurement is split into subcounters for eachestablishment cause, and for each NSI.

b) CC

c) Receipt of an RRCConnectionRequest message by the gNB from the UE.Each received RRCConnectionRequest message is added to the relevantsubcounter for the establishment cause and the relevant subcounter forthe NSI. The possible establishment causes are included in TS 38.331.The sum of all supported per cause measurements shall equal the totalnumber of RRCConnectionRequest messages. In case only a subset of percause measurements is supported, a sum subcounter will be providedfirst.

Note that the RRC message name in the trigger may be changed in laterstandard releases, but the underlying concept is the same.

d) Each measurement is an integer value.

e) The measurement name has the forms: RRC. ConnEstabAtt.Cause whereCause identifies the establishment cause; and RRC.ConnEstabAttNSI.NSIwhere NSI corresponds to the NSI ID (see TS 23.501).

f) GNBCuFunction (see TS 28.541), for the gNB 2 functional splitscenario; GNBCuCpFunction (see TS 28.541), for the gNB 3 functionalsplit scenario; and GNBFunction (see TS 28.541), for the gNB non-splitscenario.

Note that the IOC name may be revisited and aligned with the NRMdefinitions in TS 28.541.

g) Valid for packet switched traffic

h) 5GS

i) One Usage of this Measurement is for Performance Assurance.

F(2) Successful RRC Connection Establishments

a) This measurement provides the number of successful RRC connectionestablishments. This measurement is split into subcounters for eachestablishment cause, and for each NSI.

b) CC

c) Receipt of an RRCConnectionSetupComplete message by the gNB from theUE. Each received RRCConnectionSetupComplete message is added to therelevant subcounter for the establishment cause and the relevantsubcounter for the NSI. The possible establishment causes are includedin TS 38.331. The sum of all supported per cause measurements shallequal the total number of RRCConnectionSetupComplete messages. In caseonly a subset of per cause measurements is supported, a sum subcounterwill be provided first.

Note that the RRC message name in the trigger may be revisited.

d) Each measurement is an integer value.

e) The measurement name has the forms: RRC.ConnEstabSucc.Cause whereCause identifies the establishment cause; and RRC.ConnEstabSuccNSI.NSIwhere NSI corresponds to the NSI ID (see TS 23.501).

f) GNBCuFunction (see 28.541 [x]), for the gNB functional splitscenario; GNBCuCpFunction (see 28.541 [x]), for the gNB 3 functionalsplit scenario; GNBFunction (see 28.541 [x]), for the gNB non-splitscenario.

Note that the IOC name may be revisited and aligned with the NRMdefinitions in TS 28.541.

g) Valid for packet switched traffic

h) 5GS

i) One usage of this measurement is for performance assurance.

F(3) Failed RRC Connection Establishment Per Failure Cause

a) This measurement provides the number of failed RRC connectionestablishments. This measurement is split into subcounters for eachfailure cause.

b) CC

c) Transmission of an RRCConnectionReject message by the gNB from theUE. Each transmitted RRCConnectionReject message is added to therelevant subcounter for the failure cause. The possible failure causesare included in TS 38.331. The sum of all supported per causemeasurements shall equal the total number of RRCConnectionRejectmessages. In case only a subset of per cause measurements is supported,a sum subcounter will be provided first.

Note that the RRC message name in the trigger may be revisited.

d) Each measurement is an integer value.

e) The measurement name has the form RRC.ConnEstabFail.Cause where Causeidentifies the failure cause.

f) GNBCuFunction (see 28.541 [x]), for the gNB functional splitscenario; GNBCuCpFunction (see 28.541 [x]), for the gNB 3 functionalsplit scenario; GNBFunction (see 28.541 [x]), for the gNB non-splitscenario.

Note that the IOC name may be revisited and aligned with the NRMdefinitions in TS 28.541.

g) Valid for packet switched traffic

h) 5GS

i) One usage of this measurement is for performance assurance.

G. Example Embodiments

FIG. 7 illustrates an architecture of a system 700 of a network inaccordance with some embodiments. The system 700 includes one or moreuser equipment (UE), shown in this example as a UE 702 and a UE 704. TheUE 702 and the UE 704 are illustrated as smartphones (e.g., handheldtouchscreen mobile computing devices connectable to one or more cellularnetworks), but may also comprise any mobile or non-mobile computingdevice, such as Personal Data Assistants (PDAs), pagers, laptopcomputers, desktop computers, wireless handsets, or any computing deviceincluding a wireless communications interface.

In some embodiments, any of the UE 702 and the UE 704 can comprise anInternet of Things (IoT) UE, which can comprise a network access layerdesigned for low-power IoT applications utilizing short-lived UEconnections. An IoT UE can utilize technologies such asmachine-to-machine (M2M) or machine-type communications (MTC) forexchanging data with an MTC server or device via a public land mobilenetwork (PLMN), Proximity-Based Service (ProSe) or device-to-device(D2D) communication, sensor networks, or IoT networks. The M2M or MTCexchange of data may be a machine-initiated exchange of data. An IoTnetwork describes interconnecting IoT UEs, which may include uniquelyidentifiable embedded computing devices (within the Internetinfrastructure), with short-lived connections. The IoT UEs may executebackground applications (e.g., keep-alive messages, status updates,etc.) to facilitate the connections of the IoT network.

The UE 702 and the UE 704 may be configured to connect, e.g.,communicatively couple, with a radio access network (RAN), shown as RAN706. The RAN 706 may be, for example, an Evolved Universal MobileTelecommunications System (UMTS) Terrestrial Radio Access Network(E-UTRAN), a NextGen RAN (NG RAN), or some other type of RAN. The UE 702and the UE 704 utilize connection 708 and connection 710, respectively,each of which comprises a physical communications interface or layer(discussed in further detail below); in this example, the connection 708and the connection 710 are illustrated as an air interface to enablecommunicative coupling, and can be consistent with cellularcommunications protocols, such as a Global System for MobileCommunications (GSM) protocol, a code-division multiple access (CDMA)network protocol, a Push-to-Talk (PTT) protocol, a PTT over Cellular(POC) protocol, a Universal Mobile Telecommunications System (UMTS)protocol, a 3GPP Long Term Evolution (LTE) protocol, a fifth generation(5G) protocol, a New Radio (NR) protocol, and the like.

In this embodiment, the UE 702 and the UE 704 may further directlyexchange communication data via a ProSe interface 712. The ProSeinterface 712 may alternatively be referred to as a sidelink interfacecomprising one or more logical channels, including but not limited to aPhysical Sidelink Control Channel (PSCCH), a Physical Sidelink SharedChannel (PSSCH), a Physical Sidelink Discovery Channel (PSDCH), and aPhysical Sidelink Broadcast Channel (PSBCH).

The UE 704 is shown to be configured to access an access point (AP),shown as AP 714, via connection 716. The connection 716 can comprise alocal wireless connection, such as a connection consistent with any IEEE802.11 protocol, wherein the AP 714 would comprise a wireless fidelity(WiFi®) router. In this example, the AP 714 may be connected to theInternet without connecting to the core network of the wireless system(described in further detail below).

The RAN 706 can include one or more access nodes that enable theconnection 708 and the connection 710. These access nodes (ANs) can bereferred to as base stations (BSs), NodeBs, evolved NodeBs (eNBs), nextGeneration NodeBs (gNB), RAN nodes, and so forth, and can compriseground stations (e.g., terrestrial access points) or satellite stationsproviding coverage within a geographic area (e.g., a cell). The RAN 706may include one or more RAN nodes for providing macrocells, e.g., macroRAN node 718, and one or more RAN nodes for providing femtocells orpicocells (e.g., cells having smaller coverage areas, smaller usercapacity, or higher bandwidth compared to macrocells), e.g., a low power(LP) RAN node such as LP RAN node 720.

Any of the macro RAN node 718 and the LP RAN node 720 can terminate theair interface protocol and can be the first point of contact for the UE702 and the UE 704. In some embodiments, any of the macro RAN node 718and the LP RAN node 720 can fulfill various logical functions for theRAN 706 including, but not limited to, radio network controller (RNC)functions such as radio bearer management, uplink and downlink dynamicradio resource management and data packet scheduling, and mobilitymanagement.

In accordance with some embodiments, the UE 702 and the UE 704 can beconfigured to communicate using Orthogonal Frequency-DivisionMultiplexing (OFDM) communication signals with each other or with any ofthe macro RAN node 718 and the LP RAN node 720 over a multicarriercommunication channel in accordance various communication techniques,such as, but not limited to, an Orthogonal Frequency-Division MultipleAccess (OFDMA) communication technique (e.g., for downlinkcommunications) or a Single Carrier Frequency Division Multiple Access(SC-FDMA) communication technique (e.g., for uplink and ProSe orsidelink communications), although the scope of the embodiments is notlimited in this respect. The OFDM signals can comprise a plurality oforthogonal subcarriers.

In some embodiments, a downlink resource grid can be used for downlinktransmissions from any of the macro RAN node 718 and the LP RAN node 720to the UE 702 and the UE 704, while uplink transmissions can utilizesimilar techniques. The grid can be a time-frequency grid, called aresource grid or time-frequency resource grid, which is the physicalresource in the downlink in each slot. Such a time-frequency planerepresentation is a common practice for OFDM systems, which makes itintuitive for radio resource allocation. Each column and each row of theresource grid corresponds to one OFDM symbol and one OFDM subcarrier,respectively. The duration of the resource grid in the time domaincorresponds to one slot in a radio frame. The smallest time-frequencyunit in a resource grid is denoted as a resource element. Each resourcegrid comprises a number of resource blocks, which describe the mappingof certain physical channels to resource elements. Each resource blockcomprises a collection of resource elements; in the frequency domain,this may represent the smallest quantity of resources that currently canbe allocated. There are several different physical downlink channelsthat are conveyed using such resource blocks.

The physical downlink shared channel (PDSCH) may carry user data andhigher-layer signaling to the UE 702 and the UE 704. The physicaldownlink control channel (PDCCH) may carry information about thetransport format and resource allocations related to the PDSCH channel,among other things. It may also inform the UE 702 and the UE 704 aboutthe transport format, resource allocation, and H-ARQ (Hybrid AutomaticRepeat Request) information related to the uplink shared channel.Typically, downlink scheduling (assigning control and shared channelresource blocks to the UE 704 within a cell) may be performed at any ofthe macro RAN node 718 and the LP RAN node 720 based on channel qualityinformation fed back from any of the UE 702 and UE 704. The downlinkresource assignment information may be sent on the PDCCH used for (e.g.,assigned to) each of the UE 702 and the UE 704.

The PDCCH may use control channel elements (CCEs) to convey the controlinformation. Before being mapped to resource elements, the PDCCHcomplex-valued symbols may first be organized into quadruplets, whichmay then be permuted using a sub-block interleaver for rate matching.Each PDCCH may be transmitted using one or more of these CCEs, whereeach CCE may correspond to nine sets of four physical resource elementsknown as resource element groups (REGs). Four Quadrature Phase ShiftKeying (QPSK) symbols may be mapped to each REG. The PDCCH can betransmitted using one or more CCEs, depending on the size of thedownlink control information (DCI) and the channel condition. There canbe four or more different PDCCH formats defined in LTE with differentnumbers of CCEs (e.g., aggregation level, L=1, 2, 4, or 8).

Some embodiments may use concepts for resource allocation for controlchannel information that are an extension of the above-describedconcepts. For example, some embodiments may utilize an enhanced physicaldownlink control channel (EPDCCH) that uses PDSCH resources for controlinformation transmission. The EPDCCH may be transmitted using one ormore enhanced the control channel elements (ECCEs). Similar to above,each ECCE may correspond to nine sets of four physical resource elementsknown as enhanced resource element groups (EREGs). An ECCE may haveother numbers of EREGs in some situations.

The RAN 706 is communicatively coupled to a core network (CN), shown asCN 728—via an S1 interface 722. In embodiments, the CN 728 may be anevolved packet core (EPC) network, a NextGen Packet Core (NPC) network,or some other type of CN. In this embodiment the S interface 722 issplit into two parts: the S1-U interface 724, which carries traffic databetween the macro RAN node 718 and the LP RAN node 720 and a servinggateway (S-GW), shown as S-GW 732, and an S1-mobility management entity(MME) interface, shown as S1-MME interface 726, which is a signalinginterface between the macro RAN node 718 and LP RAN node 720 and theMME(s) 730.

In this embodiment, the CN 728 comprises the MME(s) 730, the S-GW 732, aPacket Data Network (PDN) Gateway (P-GW) (shown as P-GW 734), and a homesubscriber server (HSS) (shown as HSS 736). The MME(s) 730 may besimilar in function to the control plane of legacy Serving GeneralPacket Radio Service (GPRS) Support Nodes (SGSN). The MME(s) 730 maymanage mobility aspects in access such as gateway selection and trackingarea list management. The HSS 736 may comprise a database for networkusers, including subscription-related information to support the networkentities' handling of communication sessions. The CN 728 may compriseone or several HSS 736, depending on the number of mobile subscribers,on the capacity of the equipment, on the organization of the network,etc. For example, the HSS 736 can provide support for routing/roaming,authentication, authorization, naming/addressing resolution, locationdependencies, etc.

The S-GW 732 may terminate the S1 interface 322 towards the RAN 706, androutes data packets between the RAN 706 and the CN 728. In addition, theS-GW 732 may be a local mobility anchor point for inter-RAN nodehandovers and also may provide an anchor for inter-3GPP mobility. Otherresponsibilities may include lawful intercept, charging, and some policyenforcement.

The P-GW 734 may terminate an SGi interface toward a PDN. The P-GW 734may route data packets between the CN 728 (e.g., an EPC network) andexternal networks such as a network including the application server 742(alternatively referred to as application function (AF)) via an InternetProtocol (IP) interface (shown as IP communications interface 738).Generally, an application server 742 may be an element offeringapplications that use IP bearer resources with the core network (e.g.,UMTS Packet Services (PS) domain, LTE PS data services, etc.). In thisembodiment, the P-GW 734 is shown to be communicatively coupled to anapplication server 742 via an IP communications interface 738. Theapplication server 742 can also be configured to support one or morecommunication services (e.g., Voice-over-Internet Protocol (VoIP)sessions, PTT sessions, group communication sessions, social networkingservices, etc.) for the UE 702 and the UE 704 via the CN 728.

The P-GW 734 may further be a node for policy enforcement and chargingdata collection. A Policy and Charging Enforcement Function (PCRF)(shown as PCRF 740) is the policy and charging control element of the CN728. In a non-roaming scenario, there may be a single PCRF in the HomePublic Land Mobile Network (HPLMN) associated with a UE's InternetProtocol Connectivity Access Network (IP-CAN) session. In a roamingscenario with local breakout of traffic, there may be two PCRFsassociated with a UE's IP-CAN session: a Home PCRF (H-PCRF) within aHPLMN and a Visited PCRF (V-PCRF) within a Visited Public Land MobileNetwork (VPLMN). The PCRF 740 may be communicatively coupled to theapplication server 742 via the P-GW 734. The application server 742 maysignal the PCRF 740 to indicate a new service flow and select theappropriate Quality of Service (QoS) and charging parameters. The PCRF740 may provision this rule into a Policy and Charging EnforcementFunction (PCEF) (not shown) with the appropriate traffic flow template(TFT) and QoS class of identifier (QCI), which commences the QoS andcharging as specified by the application server 742.

FIG. 8 illustrates an architecture of a system 800 of a network inaccordance with some embodiments. The system 800 is shown to include aUE 802, which may be the same or similar to the UE 702 and the UE 704discussed previously; a 5G access node or RAN node (shown as (R)AN node808), which may be the same or similar to the macro RAN node 718 and/orthe LP RAN node 720 discussed previously; a User Plane Function (shownas UPF 804); a Data Network (DN 806), which may be, for example,operator services, Internet access or 3rd party services; and a 5G CoreNetwork (5GC) (shown as CN 810).

The CN 810 may include an Authentication Server Function (AUSF 814); aCore Access and Mobility Management Function (AMF 812); a SessionManagement Function (SMF 818); a Network Exposure Function (NEF 816); aPolicy Control Function (PCF 822); a Network Function (NF) RepositoryFunction (NRF 820); a Unified Data Management (UDM 824); and anApplication Function (AF 826). The CN 810 may also include otherelements that are not shown, such as a Structured Data Storage networkfunction (SDSF), an Unstructured Data Storage network function (UDSF),and the like.

The UPF 804 may act as an anchor point for intra-RAT and inter-RATmobility, an external PDU session point of interconnect to DN 806, and abranching point to support multi-homed PDU session. The UPF 804 may alsoperform packet routing and forwarding, packet inspection, enforce userplane part of policy rules, lawfully intercept packets (UP collection);traffic usage reporting, perform QoS handling for user plane (e.g.packet filtering, gating, UL/DL rate enforcement), perform UplinkTraffic verification (e.g., SDF to QoS flow mapping), transport levelpacket marking in the uplink and downlink, and downlink packet bufferingand downlink data notification triggering. UPF 804 may include an uplinkclassifier to support routing traffic flows to a data network. The DN806 may represent various network operator services, Internet access, orthird party services. DN 806 may include, or be similar to theapplication server 742 discussed previously.

The AUSF 814 may store data for authentication of UE 802 and handleauthentication related functionality. The AUSF 814 may facilitate acommon authentication framework for various access types.

The AMF 812 may be responsible for registration management (e.g., forregistering UE 802, etc.), connection management, reachabilitymanagement, mobility management, and lawful interception of AMF-relatedevents, and access authentication and authorization. AMF 812 may providetransport for SM messages for the SMF 818, and act as a transparentproxy for routing SM messages. AMF 812 may also provide transport forshort message service (SMS) messages between UE 802 and an SMS function(SMSF) (not shown by FIG. 8). AMF 812 may act as Security AnchorFunction (SEA), which may include interaction with the AUSF 814 and theUE 802, receipt of an intermediate key that was established as a resultof the UE 802 authentication process. Where USIM based authentication isused, the AMF 812 may retrieve the security material from the AUSF 814.AMF 812 may also include a Security Context Management (SCM) function,which receives a key from the SEA that it uses to derive access-networkspecific keys. Furthermore, AMF 812 may be a termination point of RAN CPinterface (N2 reference point), a termination point of NAS (NI)signaling, and perform NAS ciphering and integrity protection.

AMF 812 may also support NAS signaling with a UE 802 over an N3interworking-function (IWF) interface. The N3IWF may be used to provideaccess to untrustedentities. N3IWF may be a termination point for the N2and N3 interfaces for control plane and user plane, respectively, and assuch, may handle N2 signaling from SMF and AMF for PDU sessions and QoS,encapsulate/de-encapsulate packets for IPSec and N3 tunneling, mark N3user-plane packets in the uplink, and enforce QoS corresponding to N3packet marking taking into account QoS requirements associated to suchmarking received over N2. N3IWF may also relay uplink and downlinkcontrol-plane NAS (NI) signaling between the UE 802 and AMF 812, andrelay uplink and downlink user-plane packets between the UE 802 and UPF804. The N3IWF also provides mechanisms for IPsec tunnel establishmentwith the UE 802.

The SMF 818 may be responsible for session management (e.g., sessionestablishment, modify and release, including tunnel maintain between UPFand AN node); UE IP address allocation & management (including optionalAuthorization); Selection and control of UP function; Configures trafficsteering at UPF to route traffic to proper destination; termination ofinterfaces towards Policy control functions; control part of policyenforcement and QoS; lawful intercept (for SM events and interface to LISystem); termination of SM parts of NAS messages; downlink DataNotification; initiator of AN specific SM information, sent via AMF overN2 to AN; determine SSC mode of a session. The SMF 818 may include thefollowing roaming functionality: handle local enforcement to apply QoSSLAs (VPLMN); charging data collection and charging interface (VPLMN);lawful intercept (in VPLMN for SM events and interface to LI System);support for interaction with external DN for transport of signaling forPDU session authorization/authentication by external DN.

The NEF 816 may provide means for securely exposing the services andcapabilities provided by 3GPP network functions for third party,internal exposure/re-exposure, Application Functions (e.g., AF 826),edge computing or fog computing systems, etc. In such embodiments, theNEF 816 may authenticate, authorize, and/or throttle the AFs. NEF 816may also translate information exchanged with the AF 826 and informationexchanged with internal network functions. For example, the NEF 816 maytranslate between an AF-Service-Identifier and an internal 5GCinformation. NEF 816 may also receive information from other networkfunctions (NFs) based on exposed capabilities of other networkfunctions. This information may be stored at the NEF 816 as structureddata, or at a data storage NF using a standardized interfaces. Thestored information can then be re-exposed by the NEF 816 to other NFsand AFs, and/or used for other purposes such as analytics.

The NRF 820 may support service discovery functions, receive NFDiscovery Requests from NF instances, and provide the information of thediscovered NF instances to the NF instances. NRF 820 also maintainsinformation of available NF instances and their supported services.

The PCF 822 may provide policy rules to control plane function(s) toenforce them, and may also support unified policy framework to governnetwork behavior. The PCF 822 may also implement a front end (FE) toaccess subscription information relevant for policy decisions in a UDRof UDM 824.

The UDM 824 may handle subscription-related information to support thenetwork entities' handling of communication sessions, and may storesubscription data of UE 802. The UDM 824 may include two parts, anapplication FE and a User Data Repository (UDR). The UDM may include aUDM FE, which is in charge of processing of credentials, locationmanagement, subscription management and so on. Several different frontends may serve the same user in different transactions. The UDM-FEaccesses subscription information stored in the UDR and performsauthentication credential processing; user identification handling;access authorization; registration/mobility management; and subscriptionmanagement. The UDR may interact with PCF 822. UDM 824 may also supportSMS management, wherein an SMS-FE implements the similar applicationlogic as discussed previously.

The AF 826 may provide application influence on traffic routing, accessto the Network Capability Exposure (NCE), and interact with the policyframework for policy control. The NCE may be a mechanism that allows the5GC and AF 826 to provide information to each other via NEF 816, whichmay be used for edge computing implementations. In such implementations,the network operator and third party services may be hosted close to theUE 802 access point of attachment to achieve an efficient servicedelivery through the reduced end-to-end latency and load on thetransport network. For edge computing implementations, the 5GC mayselect a UPF 804 close to the UE 802 and execute traffic steering fromthe UPF 804 to DN 806 via the N6 interface. This may be based on the UEsubscription data, UE location, and information provided by the AF 826.In this way, the AF 826 may influence UPF (re)selection and trafficrouting. Based on operator deployment, when AF 826 is considered to be atrusted entity, the network operator may permit AF 826 to interactdirectly with relevant NFs.

As discussed previously, the CN 810 may include an SMSF, which may beresponsible for SMS subscription checking and verification, and relayingSM messages to/from the UE 802 to/from other entities, such as anSMS-GMSC/IWMSC/SMS-router. The SMS may also interact with AMF 812 andUDM 824 for notification procedure that the UE 802 is available for SMStransfer (e.g., set a UE not reachable flag, and notifying UDM 824 whenUE 802 is available for SMS).

The system 800 may include the following service-based interfaces: Namf:Service-based interface exhibited by AMF; Nsmf: Service-based interfaceexhibited by SMF; Nnef: Service-based interface exhibited by NEF; Npcf:Service-based interface exhibited by PCF; Nudm: Service-based interfaceexhibited by UDM; Naf: Service-based interface exhibited by AF; Nnrf:Service-based interface exhibited by NRF; and Nausf: Service-basedinterface exhibited by AUSF.

The system 800 may include the following reference points: N1: Referencepoint between the UE and the AMF; N2: Reference point between the (R)ANand the AMF; N3: Reference point between the (R)AN and the UPF; N4:Reference point between the SMF and the UPF; and N6: Reference pointbetween the UPF and a Data Network. There may be many more referencepoints and/or service-based interfaces between the NF services in theNFs, however, these interfaces and reference points have been omittedfor clarity. For example, an NS reference point may be between the PCFand the AF; an N7 reference point may be between the PCF and the SMF; anN11 reference point between the AMF and SMF; etc. In some embodiments,the CN 810 may include an Nx interface, which is an inter-CN interfacebetween the MME (e.g., MME(s) 730) and the AMF 812 in order to enableinterworking between CN 810 and CN 728.

Although not shown by FIG. 8, the system 800 may include multiple RANnodes (such as (R)AN node 808) wherein an Xn interface is definedbetween two or more (R)AN node 808 (e.g., gNBs and the like) thatconnecting to 5GC 410, between a (R)AN node 808 (e.g., gNB) connectingto CN 810 and an eNB (e.g., a macro RAN node 718 of FIG. 7), and/orbetween two eNBs connecting to CN 810.

In some implementations, the Xn interface may include an Xn user plane(Xn-U) interface and an Xn control plane (Xn-C) interface. The Xn-U mayprovide non-guaranteed delivery of user plane PDUs and support/providedata forwarding and flow control functionality. The Xn-C may providemanagement and error handling functionality, functionality to manage theXn-C interface; mobility support for UE 802 in a connected mode (e.g.,CM-CONNECTED) including functionality to manage the UE mobility forconnected mode between one or more (R)AN node 808. The mobility supportmay include context transfer from an old (source) serving (R)AN node 808to new (target) serving (R)AN node 808; and control of user planetunnels between old (source) serving (R)AN node 808 to new (target)serving (R)AN node 808.

A protocol stack of the Xn-U may include a transport network layer builton Internet Protocol (IP) transport layer, and a GTP-U layer on top of aUDP and/or IP layer(s) to carry user plane PDUs. The Xn-C protocol stackmay include an application layer signaling protocol (referred to as XnApplication Protocol (Xn-AP)) and a transport network layer that isbuilt on an SCTP layer. The SCTP layer may be on top of an IP layer. TheSCTP layer provides the guaranteed delivery of application layermessages. In the transport IP layer point-to-point transmission is usedto deliver the signaling PDUs. In other implementations, the Xn-Uprotocol stack and/or the Xn-C protocol stack may be same or similar tothe user plane and/or control plane protocol stack(s) shown anddescribed herein.

FIG. 9 illustrates example components of a device 900 in accordance withsome embodiments. In some embodiments, the device 900 may includeapplication circuitry 902, baseband circuitry 904, Radio Frequency (RF)circuitry (shown as RF circuitry 920), front-end module (FEM) circuitry(shown as FEM circuitry 930), one or more antennas 932, and powermanagement circuitry (PMC) (shown as PMC 934) coupled together at leastas shown. The components of the illustrated device 900 may be includedin a UE or a RAN node. In some embodiments, the device 900 may includefewer elements (e.g., a RAN node may not utilize application circuitry902, and instead include a processor/controller to process IP datareceived from an EPC). In some embodiments, the device 900 may includeadditional elements such as, for example, memory/storage, display,camera, sensor, or input/output (I/O) interface. In other embodiments,the components described below may be included in more than one device(e.g., said circuitries may be separately included in more than onedevice for Cloud-RAN (C-RAN) implementations).

The application circuitry 902 may include one or more applicationprocessors. For example, the application circuitry 902 may includecircuitry such as, but not limited to, one or more single-core ormulti-core processors. The processor(s) may include any combination ofgeneral-purpose processors and dedicated processors (e.g., graphicsprocessors, application processors, etc.). The processors may be coupledwith or may include memory/storage and may be configured to executeinstructions stored in the memory/storage to enable various applicationsor operating systems to run on the device 900. In some embodiments,processors of application circuitry 902 may process IP data packetsreceived from an EPC.

The baseband circuitry 904 may include circuitry such as, but notlimited to, one or more single-core or multi-core processors. Thebaseband circuitry 904 may include one or more baseband processors orcontrol logic to process baseband signals received from a receive signalpath of the RF circuitry 920 and to generate baseband signals for atransmit signal path of the RF circuitry 920. The baseband circuitry 904may interface with the application circuitry 902 for generation andprocessing of the baseband signals and for controlling operations of theRF circuitry 920. For example, in some embodiments, the basebandcircuitry 904 may include a third generation (3G) baseband processor (3Gbaseband processor 906), a fourth generation (4G) baseband processor (4Gbaseband processor 908), a fifth generation (5G) baseband processor (5Gbaseband processor 910), or other baseband processor(s) 912 for otherexisting generations, generations in development or to be developed inthe future (e.g., second generation (2G), sixth generation (6G), etc.).The baseband circuitry 904 (e.g., one or more of baseband processors)may handle various radio control functions that enable communicationwith one or more radio networks via the RF circuitry 920. In otherembodiments, some or all of the functionality of the illustratedbaseband processors may be included in modules stored in the memory 918and executed via a Central Processing Unit (CPU 914). The radio controlfunctions may include, but are not limited to, signalmodulation/demodulation, encoding/decoding, radio frequency shifting,etc. In some embodiments, modulation/demodulation circuitry of thebaseband circuitry 904 may include Fast-Fourier Transform (FFT),precoding, or constellation mapping/demapping functionality. In someembodiments, encoding/decoding circuitry of the baseband circuitry 904may include convolution, tail-biting convolution, turbo, Viterbi, or LowDensity Parity Check (LDPC) encoder/decoder functionality. Embodimentsof modulation/demodulation and encoder/decoder functionality are notlimited to these examples and may include other suitable functionalityin other embodiments.

In some embodiments, the baseband circuitry 904 may include a digitalsignal processor (DSP), such as one or more audio DSP(s) 916. The one ormore audio DSP(s) 916 may be include elements forcompression/decompression and echo cancellation and may include othersuitable processing elements in other embodiments. Components of thebaseband circuitry may be suitably combined in a single chip, a singlechipset, or disposed on a same circuit board in some embodiments. Insome embodiments, some or all of the constituent components of thebaseband circuitry 904 and the application circuitry 902 may beimplemented together such as, for example, on a system on a chip (SOC).

In some embodiments, the baseband circuitry 904 may provide forcommunication compatible with one or more radio technologies. Forexample, in some embodiments, the baseband circuitry 904 may supportcommunication with an evolved universal terrestrial radio access network(EUTRAN) or other wireless metropolitan area networks (WMAN), a wirelesslocal area network (WLAN), or a wireless personal area network (WPAN).Embodiments in which the baseband circuitry 904 is configured to supportradio communications of more than one wireless protocol may be referredto as multi-mode baseband circuitry.

The RF circuitry 920 may enable communication with wireless networksusing modulated electromagnetic radiation through a non-solid medium. Invarious embodiments, the RF circuitry 920 may include switches, filters,amplifiers, etc. to facilitate the communication with the wirelessnetwork. The RF circuitry 920 may include a receive signal path whichmay include circuitry to down-convert RF signals received from the FEMcircuitry 930 and provide baseband signals to the baseband circuitry904. The RF circuitry 920 may also include a transmit signal path whichmay include circuitry to up-convert baseband signals provided by thebaseband circuitry 904 and provide RF output signals to the FEMcircuitry 930 for transmission.

In some embodiments, the receive signal path of the RF circuitry 920 mayinclude mixer circuitry 922, amplifier circuitry 924 and filtercircuitry 926. In some embodiments, the transmit signal path of the RFcircuitry 920 may include filter circuitry 926 and mixer circuitry 922.The RF circuitry 920 may also include synthesizer circuitry 928 forsynthesizing a frequency for use by the mixer circuitry 922 of thereceive signal path and the transmit signal path. In some embodiments,the mixer circuitry 922 of the receive signal path may be configured todown-convert RF signals received from the FEM circuitry 930 based on thesynthesized frequency provided by synthesizer circuitry 928. Theamplifier circuitry 924 may be configured to amplify the down-convertedsignals and the filter circuitry 926 may be a low-pass filter (LPF) orband-pass filter (BPF) configured to remove unwanted signals from thedown-converted signals to generate output baseband signals. Outputbaseband signals may be provided to the baseband circuitry 904 forfurther processing. In some embodiments, the output baseband signals maybe zero-frequency baseband signals, although this is not a requirement.In some embodiments, the mixer circuitry 922 of the receive signal pathmay comprise passive mixers, although the scope of the embodiments isnot limited in this respect.

In some embodiments, the mixer circuitry 922 of the transmit signal pathmay be configured to up-convert input baseband signals based on thesynthesized frequency provided by the synthesizer circuitry 928 togenerate RF output signals for the FEM circuitry 930. The basebandsignals may be provided by the baseband circuitry 904 and may befiltered by the filter circuitry 926.

In some embodiments, the mixer circuitry 922 of the receive signal pathand the mixer circuitry 922 of the transmit signal path may include twoor more mixers and may be arranged for quadrature downconversion andupconversion, respectively. In some embodiments, the mixer circuitry 922of the receive signal path and the mixer circuitry 922 of the transmitsignal path may include two or more mixers and may be arranged for imagerejection (e.g., Hartley image rejection). In some embodiments, themixer circuitry 922 of the receive signal path and the mixer circuitry922 may be arranged for direct downconversion and direct upconversion,respectively. In some embodiments, the mixer circuitry 922 of thereceive signal path and the mixer circuitry 922 of the transmit signalpath may be configured for super-heterodyne operation.

In some embodiments, the output baseband signals and the input basebandsignals may be analog baseband signals, although the scope of theembodiments is not limited in this respect. In some alternateembodiments, the output baseband signals and the input baseband signalsmay be digital baseband signals. In these alternate embodiments, the RFcircuitry 920 may include analog-to-digital converter (ADC) anddigital-to-analog converter (DAC) circuitry and the baseband circuitry904 may include a digital baseband interface to communicate with the RFcircuitry 920.

In some dual-mode embodiments, a separate radio IC circuitry may beprovided for processing signals for each spectrum, although the scope ofthe embodiments is not limited in this respect.

In some embodiments, the synthesizer circuitry 928 may be a fractional-Nsynthesizer or a fractional N/N+1 synthesizer, although the scope of theembodiments is not limited in this respect as other types of frequencysynthesizers may be suitable. For example, synthesizer circuitry 928 maybe a delta-sigma synthesizer, a frequency multiplier, or a synthesizercomprising a phase-locked loop with a frequency divider.

The synthesizer circuitry 928 may be configured to synthesize an outputfrequency for use by the mixer circuitry 922 of the RF circuitry 920based on a frequency input and a divider control input. In someembodiments, the synthesizer circuitry 928 may be a fractional N/N+1synthesizer.

In some embodiments, frequency input may be provided by a voltagecontrolled oscillator (VCO), although that is not a requirement. Dividercontrol input may be provided by either the baseband circuitry 904 orthe application circuitry 902 (such as an applications processor)depending on the desired output frequency. In some embodiments, adivider control input (e.g., N) may be determined from a look-up tablebased on a channel indicated by the application circuitry 902.

Synthesizer circuitry 928 of the RF circuitry 920 may include a divider,a delay-locked loop (DLL), a multiplexer and a phase accumulator. Insome embodiments, the divider may be a dual modulus divider (DMD) andthe phase accumulator may be a digital phase accumulator (DPA). In someembodiments, the DMD may be configured to divide the input signal byeither N or N+1 (e.g., based on a carry out) to provide a fractionaldivision ratio. In some example embodiments, the DLL may include a setof cascaded, tunable, delay elements, a phase detector, a charge pumpand a D-type flip-flop. In these embodiments, the delay elements may beconfigured to break a VCO period up into Nd equal packets of phase,where Nd is the number of delay elements in the delay line. In this way,the DLL provides negative feedback to help ensure that the total delaythrough the delay line is one VCO cycle.

In some embodiments, the synthesizer circuitry 928 may be configured togenerate a carrier frequency as the output frequency, while in otherembodiments, the output frequency may be a multiple of the carrierfrequency (e.g., twice the carrier frequency, four times the carrierfrequency) and used in conjunction with quadrature generator and dividercircuitry to generate multiple signals at the carrier frequency withmultiple different phases with respect to each other. In someembodiments, the output frequency may be a LO frequency (fLO). In someembodiments, the RF circuitry 920 may include an IQ/polar converter.

The FEM circuitry 930 may include a receive signal path which mayinclude circuitry configured to operate on RF signals received from oneor more antennas 932, amplify the received signals and provide theamplified versions of the received signals to the RF circuitry 920 forfurther processing. The FEM circuitry 930 may also include a transmitsignal path which may include circuitry configured to amplify signalsfor transmission provided by the RF circuitry 920 for transmission byone or more of the one or more antennas 932. In various embodiments, theamplification through the transmit or receive signal paths may be donesolely in the RF circuitry 920, solely in the FEM circuitry 930, or inboth the RF circuitry 920 and the FEM circuitry 930.

In some embodiments, the FEM circuitry 930 may include a TX/RX switch toswitch between transmit mode and receive mode operation. The FEMcircuitry 930 may include a receive signal path and a transmit signalpath. The receive signal path of the FEM circuitry 930 may include anLNA to amplify received RF signals and provide the amplified received RFsignals as an output (e.g., to the RF circuitry 920). The transmitsignal path of the FEM circuitry 930 may include a power amplifier (PA)to amplify input RF signals (e.g., provided by the RF circuitry 920),and one or more filters to generate RF signals for subsequenttransmission (e.g., by one or more of the one or more antennas 932).

In some embodiments, the PMC 934 may manage power provided to thebaseband circuitry 904. In particular, the PMC 934 may controlpower-source selection, voltage scaling, battery charging, or DC-to-DCconversion. The PMC 934 may often be included when the device 900 iscapable of being powered by a battery, for example, when the device 900is included in a UE. The PMC 934 may increase the power conversionefficiency while providing desirable implementation size and heatdissipation characteristics.

FIG. 9 shows the PMC 934 coupled only with the baseband circuitry 904.However, in other embodiments, the PMC 934 may be additionally oralternatively coupled with, and perform similar power managementoperations for, other components such as, but not limited to, theapplication circuitry 902, the RF circuitry 920, or the FEM circuitry930.

In some embodiments, the PMC 934 may control, or otherwise be part of,various power saving mechanisms of the device 900. For example, if thedevice 900 is in an RRC_Connected state, where it is still connected tothe RAN node as it expects to receive traffic shortly, then it may entera state known as Discontinuous Reception Mode (DRX) after a period ofinactivity. During this state, the device 900 may power down for briefintervals of time and thus save power.

If there is no data traffic activity for an extended period of time,then the device 900 may transition off to an RRC_Idle state, where itdisconnects from the network and does not perform operations such aschannel quality feedback, handover, etc. The device 900 goes into a verylow power state and it performs paging where again it periodically wakesup to listen to the network and then powers down again. The device 900may not receive data in this state, and in order to receive data, ittransitions back to an RRC_Connected state.

An additional power saving mode may allow a device to be unavailable tothe network for periods longer than a paging interval (ranging fromseconds to a few hours). During this time, the device is totallyunreachable to the network and may power down completely. Any data sentduring this time incurs a large delay and it is assumed the delay isacceptable.

Processors of the application circuitry 902 and processors of thebaseband circuitry 904 may be used to execute elements of one or moreinstances of a protocol stack. For example, processors of the basebandcircuitry 904, alone or in combination, may be used to execute Layer 3,Layer 2, or Layer 1 functionality, while processors of the applicationcircuitry 902 may utilize data (e.g., packet data) received from theselayers and further execute Layer 4 functionality (e.g., transmissioncommunication protocol (TCP) and user datagram protocol (UDP) layers).As referred to herein, Layer 3 may comprise a radio resource control(RRC) layer, described in further detail below. As referred to herein,Layer 2 may comprise a medium access control (MAC) layer, a radio linkcontrol (RLC) layer, and a packet data convergence protocol (PDCP)layer, described in further detail below. As referred to herein, Layer 1may comprise a physical (PHY) layer of a UE/RAN node, described infurther detail below.

FIG. 10 illustrates example interfaces 1000 of baseband circuitry inaccordance with some embodiments. As discussed above, the basebandcircuitry 904 of FIG. 9 may comprise 3G baseband processor 906, 4Gbaseband processor 908, 5G baseband processor 910, other basebandprocessor(s) 912, CPU 914, and a memory 918 utilized by said processors.As illustrated, each of the processors may include a respective memoryinterface 1002 to send/receive data to/from the memory 918.

The baseband circuitry 904 may further include one or more interfaces tocommunicatively couple to other circuitries/devices, such as a memoryinterface 1004 (e.g., an interface to send/receive data to/from memoryexternal to the baseband circuitry 904), an application circuitryinterface 1006 (e.g., an interface to send/receive data to/from theapplication circuitry 902 of FIG. 9), an RF circuitry interface 1008(e.g., an interface to send/receive data to/from RF circuitry 920 ofFIG. 9), a wireless hardware connectivity interface 1010 (e.g., aninterface to send/receive data to/from Near Field Communication (NFC)components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi®components, and other communication components), and a power managementinterface 1012 (e.g., an interface to send/receive power or controlsignals to/from the PMC 934.

FIG. 11 is an illustration of a control plane protocol stack inaccordance with some embodiments. In this embodiment, a control plane1100 is shown as a communications protocol stack between the UE 702 (oralternatively, the UE 704), the RAN 706 (e.g., the macro RAN node 718and/or the LP RAN node 720), and the MME(s) 730.

A PHY layer 1102 may transmit or receive information used by the MAClayer 1104 over one or more air interfaces. The PHY layer 1102 mayfurther perform link adaptation or adaptive modulation and coding (AMC),power control, cell search (e.g., for initial synchronization andhandover purposes), and other measurements used by higher layers, suchas an RRC layer 1110. The PHY layer 1102 may still further perform errordetection on the transport channels, forward error correction (FEC)coding/decoding of the transport channels, modulation/demodulation ofphysical channels, interleaving, rate matching, mapping onto physicalchannels, and Multiple Input Multiple Output (MIMO) antenna processing.

The MAC layer 1104 may perform mapping between logical channels andtransport channels, multiplexing of MAC service data units (SDUs) fromone or more logical channels onto transport blocks (TB) to be deliveredto PHY via transport channels, de-multiplexing MAC SDUs to one or morelogical channels from transport blocks (TB) delivered from the PHY viatransport channels, multiplexing MAC SDUs onto TBs, schedulinginformation reporting, error correction through hybrid automatic repeatrequest (HARQ), and logical channel prioritization.

An RLC layer 1106 may operate in a plurality of modes of operation,including: Transparent Mode (TM), Unacknowledged Mode (UM), andAcknowledged Mode (AM). The RLC layer 1106 may execute transfer of upperlayer protocol data units (PDUs), error correction through automaticrepeat request (ARQ) for AM data transfers, and concatenation,segmentation and reassembly of RLC SDUs for UM and AM data transfers.The RLC layer 1106 may also execute re-segmentation of RLC data PDUs forAM data transfers, reorder RLC data PDUs for UM and AM data transfers,detect duplicate data for UM and AM data transfers, discard RLC SDUs forUM and AM data transfers, detect protocol errors for AM data transfers,and perform RLC re-establishment.

A PDCP layer 1108 may execute header compression and decompression of IPdata, maintain PDCP Sequence Numbers (SNs), perform in-sequence deliveryof upper layer PDUs at re-establishment of lower layers, eliminateduplicates of lower layer SDUs at re-establishment of lower layers forradio bearers mapped on RLC AM, cipher and decipher control plane data,perform integrity protection and integrity verification of control planedata, control timer-based discard of data, and perform securityoperations (e.g., ciphering, deciphering, integrity protection,integrity verification, etc.).

The main services and functions of the RRC layer 1110 may includebroadcast of system information (e.g., included in Master InformationBlocks (MIBs) or System Information Blocks (SIBs) related to thenon-access stratum (NAS)), broadcast of system information related tothe access stratum (AS), paging, establishment, maintenance and releaseof an RRC connection between the UE and E-UTRAN (e.g., RRC connectionpaging, RRC connection establishment, RRC connection modification, andRRC connection release), establishment, configuration, maintenance andrelease of point-to-point radio bearers, security functions includingkey management, inter radio access technology (RAT) mobility, andmeasurement configuration for UE measurement reporting. Said MIBs andSIBs may comprise one or more information elements (IEs), which may eachcomprise individual data fields or data structures.

The UE 702 and the RAN 706 may utilize a Uu interface (e.g., an LTE-Uuinterface) to exchange control plane data via a protocol stackcomprising the PHY layer 1102, the MAC layer 1104, the RLC layer 1106,the PDCP layer 1108, and the RRC layer 1110.

In the embodiment shown, the non-access stratum (NAS) protocols (NASprotocols 1112) form the highest stratum of the control plane betweenthe UE 702 and the MME(s) 730. The NAS protocols 1112 support themobility of the UE 702 and the session management procedures toestablish and maintain IP connectivity between the UE 702 and the P-GW734.

The S1 Application Protocol (S1-AP) layer (S1-AP layer 1122) may supportthe functions of the S1 interface and comprise Elementary Procedures(EPs). An EP is a unit of interaction between the RAN 706 and the CN728. The S1-AP layer services may comprise two groups: UE-associatedservices and non UE-associated services. These services performfunctions including, but not limited to: E-UTRAN Radio Access Bearer(E-RAB) management, UE capability indication, mobility, NAS signalingtransport, RAN Information Management (RIM), and configuration transfer.

The Stream Control Transmission Protocol (SCTP) layer (alternativelyreferred to as the stream control transmission protocol/internetprotocol (SCTP/IP) layer) (SCTP layer 1120) may ensure reliable deliveryof signaling messages between the RAN 706 and the MME(s) 730 based, inpart, on the IP protocol, supported by an IP layer 1118. An L2 layer1116 and an L1 layer 1114 may refer to communication links (e.g., wiredor wireless) used by the RAN node and the MME to exchange information.

The RAN 706 and the MME(s) 730 may utilize an S1-MME interface toexchange control plane data via a protocol stack comprising the L1 layer1114, the L2 layer 1116, the IP layer 1118, the SCTP layer 1120, and theS1-AP layer 1122.

FIG. 12 is an illustration of a user plane protocol stack in accordancewith some embodiments. In this embodiment, a user plane 1200 is shown asa communications protocol stack between the UE 702 (or alternatively,the UE 704), the RAN 706 (e.g., the macro RAN node 718 and/or the LP RANnode 720), the S-GW 732, and the P-GW 734. The user plane 1200 mayutilize at least some of the same protocol layers as the control plane1100. For example, the UE 702 and the RAN 706 may utilize a Uu interface(e.g., an LTE-Uu interface) to exchange user plane data via a protocolstack comprising the PHY layer 1102, the MAC layer 1104, the RLC layer1106, the PDCP layer 1108.

The General Packet Radio Service (GPRS) Tunneling Protocol for the userplane (GTP-U) layer (GTP-U layer 1204) may be used for carrying userdata within the GPRS core network and between the radio access networkand the core network. The user data transported can be packets in any ofIPv4, IPv6, or PPP formats, for example. The UDP and IP security(UDP/IP) layer (UDP/IP layer 1202) may provide checksums for dataintegrity, port numbers for addressing different functions at the sourceand destination, and encryption and authentication on the selected dataflows. The RAN 706 and the S-GW 732 may utilize an S1-U interface toexchange user plane data via a protocol stack comprising the L1 layer1114, the L2 layer 1116, the UDP/IP layer 1202, and the GTP-U layer1204. The S-GW 732 and the P-GW 734 may utilize an S5/S8a interface toexchange user plane data via a protocol stack comprising the L1 layer1114, the L2 layer 1116, the UDP/IP layer 1202, and the GTP-U layer1204. As discussed above with respect to FIG. 11, NAS protocols supportthe mobility of the UE 702 and the session management procedures toestablish and maintain IP connectivity between the UE 702 and the P-GW734.

FIG. 13 illustrates components 1300 of a core network in accordance withsome embodiments. The components of the CN 728 may be implemented in onephysical node or separate physical nodes including components to readand execute instructions from a machine-readable or computer-readablemedium (e.g., a non-transitory machine-readable storage medium). In someembodiments, Network Functions Virtualization (NFV) is utilized tovirtualize any or all of the above described network node functions viaexecutable instructions stored in one or more computer readable storagemediums (described in further detail below). A logical instantiation ofthe CN 728 may be referred to as a network slice 1302 (e.g., the networkslice 1302 is shown to include the HSS 736, the MME(s) 730, and the S-GW732). A logical instantiation of a portion of the CN 728 may be referredto as a network sub-slice 1304 (e.g., the network sub-slice 1304 isshown to include the P-GW 734 and the PCRF 740).

NFV architectures and infrastructures may be used to virtualize one ormore network functions, alternatively performed by proprietary hardware,onto physical resources comprising a combination of industry-standardserver hardware, storage hardware, or switches. In other words, NFVsystems can be used to execute virtual or reconfigurable implementationsof one or more EPC components/functions.

FIG. 14 is a block diagram illustrating components, according to someexample embodiments, of a system 1400 to support NFV. The system 1400 isillustrated as including a virtualized infrastructure manager (shown asVIM 1402), a network function virtualization infrastructure (shown asNFVI 1404), a VNF manager (shown as VNFM 1406), virtualized networkfunctions (shown as VNF 1408), an element manager (shown as EM 1410), anNFV Orchestrator (shown as NFVO 1412), and a network manager (shown asNM 1414).

The VIM 1402 manages the resources of the NFVI 1404. The NFVI 1404 caninclude physical or virtual resources and applications (includinghypervisors) used to execute the system 1400. The VIM 1402 may managethe life cycle of virtual resources with the NFVI 1404 (e.g., creation,maintenance, and tear down of virtual machines (VMs) associated with oneor more physical resources), track VM instances, track performance,fault and security of VM instances and associated physical resources,and expose VM instances and associated physical resources to othermanagement systems.

The VNFM 1406 may manage the VNF 1408. The VNF 1408 may be used toexecute EPC components/functions. The VNFM 1406 may manage the lifecycle of the VNF 1408 and track performance, fault and security of thevirtual aspects of VNF 1408. The EM 1410 may track the performance,fault and security of the functional aspects of VNF 1408. The trackingdata from the VNFM 1406 and the EM 1410 may comprise, for example,performance measurement (PM) data used by the VIM 1402 or the NFVI 1404.Both the VNFM 1406 and the EM 1410 can scale up/down the quantity ofVNFs of the system 1400.

The NFVO 1412 may coordinate, authorize, release and engage resources ofthe NFVI 1404 in order to provide the requested service (e.g., toexecute an EPC function, component, or slice). The NM 1414 may provide apackage of end-user functions with the responsibility for the managementof a network, which may include network elements with VNFs,non-virtualized network functions, or both (management of the VNFs mayoccur via the EM 1410).

FIG. 15 is a block diagram illustrating components 1500, according tosome example embodiments, able to read instructions from amachine-readable or computer-readable medium (e.g., a non-transitorymachine-readable storage medium) and perform any one or more of themethodologies discussed herein. Specifically, FIG. 15 shows adiagrammatic representation of hardware resources 1502 including one ormore processors 1512 (or processor cores), one or more memory/storagedevices 1518, and one or more communication resources 1520, each ofwhich may be communicatively coupled via a bus 1522. For embodimentswhere node virtualization (e.g., NFV) is utilized, a hypervisor 1504 maybe executed to provide an execution environment for one or more networkslices/sub-slices to utilize the hardware resources 1502.

The processors 1512 (e.g., a central processing unit (CPU), a reducedinstruction set computing (RISC) processor, a complex instruction setcomputing (CISC) processor, a graphics processing unit (GPU), a digitalsignal processor (DSP) such as a baseband processor, an applicationspecific integrated circuit (ASIC), a radio-frequency integrated circuit(RFIC), another processor, or any suitable combination thereof) mayinclude, for example, a processor 1514 and a processor 1516.

The memory/storage devices 1518 may include main memory, disk storage,or any suitable combination thereof. The memory/storage devices 1518 mayinclude, but are not limited to any type of volatile or non-volatilememory such as dynamic random access memory (DRAM), static random-accessmemory (SRAM), erasable programmable read-only memory (EPROM),electrically erasable programmable read-only memory (EEPROM), Flashmemory, solid-state storage, etc.

The communication resources 1520 may include interconnection or networkinterface components or other suitable devices to communicate with oneor more peripheral devices 1506 or one or more databases 1508 via anetwork 1510. For example, the communication resources 1520 may includewired communication components (e.g., for coupling via a UniversalSerial Bus (USB)), cellular communication components, NFC components,Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components,and other communication components.

Instructions 1524 may comprise software, a program, an application, anapplet, an app, or other executable code for causing at least any of theprocessors 1512 to perform any one or more of the methodologiesdiscussed herein. The instructions 1524 may reside, completely orpartially, within at least one of the processors 1512 (e.g., within theprocessor's cache memory), the memory/storage devices 1518, or anysuitable combination thereof. Furthermore, any portion of theinstructions 1524 may be transferred to the hardware resources 1502 fromany combination of the peripheral devices 1506 or the databases 1508.Accordingly, the memory of the processors 1512, the memory/storagedevices 1518, the peripheral devices 1506, and the databases 1508 areexamples of computer-readable and machine-readable media.

H. Further Examples

The following examples pertain to further embodiments.

Example 1A is a method for a service producer in a wireless network toprovide performance management related service for one or more networkfunction (NF). The method include receiving a measurement job creationrequest, from an authorized consumer, to create a measurement job tocollect performance data of the one or more NF; and in response to themeasurement job creation request, requesting the one or more NF tocollect the performance data, wherein the measurement job creationrequest indicates whether the performance data is to be reported byperformance data file or by performance data streaming.

Example 2A includes the method of Example 1A, further comprising, inresponse to creation of the measurement job for the one or more NF,generating the performance data for the measurement job.

Example 3A is the method of Example 1A, wherein the service producercomprises a network function management function (NFMF) in the wirelessnetwork.

Example 4A is the method of Example 3A, wherein the NFMF comprises anetwork function performance management function (NFPMF).

Example 5A is the method of Example 1A, wherein the service producercomprises an NF measurement job control service producer.

Example 6A is the method of Example 1A, further comprising: receiving aquery, from the authorized consumer, to report information about one ormore ongoing NF measurement job corresponding to the authorizedconsumer; and in response to the query, providing the information aboutthe one or more ongoing NF measurement job to the authorized consumer.

Example 7A is the method of Example 1A, further comprising: if themeasurement job creation request indicates that the performance data isto be reported by the performance data file, sending a performance datafile ready notification to the authorized consumer; and if themeasurement job creation request indicates that the performance data isto be reported by the performance data streaming, sending a performancedata stream to the authorized consumer. In certain embodiments, themethod of Example 1A may be performed by a first apparatus and themethod of Example 7A may be performed by a second apparatus.

Example 8A is a method for a network slice subnet instance (NSSI)measurement job control service. The method includes: receiving arequest to create an NSSI measurement job to collect performance data ofone or more NSSI; decomposing the performance data of the one or moreNSSI into performance data types of constituent NSSIs and/or networkfunctions (NFs); determining whether the performance data types of theconstituent NSSI(s) and/or NFs can be collected by existing measurementjobs, if any, for the constituent NSSI(s) and/or NFs; and in response todetermining that the performance data types cannot be collected by theexisting measurement jobs for the constituent NSSI(s) and/or NFs,creating one or more new measurement jobs for the constituent NSSI(s)and/or NFs, respectively.

Example 9A is the method of Example 8A, wherein creating the one or morenew measurement jobs comprises: requesting the respective constituentNSSIs and/or NFs to collect the performance data, wherein the requestindicates whether the performance data is to be reported by performancedata file or by performance data streaming.

Example 10A is the method of Example 8A, wherein the method is performedby a service producer configured to provide a performance managementservice for NSSI.

Example 1A is the method of Example 10A, wherein the service producercomprises a network function performance management function (NFPMF) ora network function (NF).

Example 12A is the method of Example 10A, wherein the service producercomprises an NSSI measurement job control service producer.

Example 13A is the method of Example 8A, further comprising: receiving aquery, from an authorized consumer, to report information about one ormore ongoing NSSI measurement job corresponding to the authorizedconsumer; and in response to the query, providing the information aboutthe one or more ongoing NSSI measurement job to the authorized consumer.

Example 14A is the method of Example 8A, further comprising one of:sending an NSSI performance data file ready notification to anauthorized consumer; or sending an NSSI performance data stream to theauthorized consumer. In certain embodiments, the method of Example 8Amay be performed by a first apparatus and the method of Example 14A maybe performed by a second apparatus.

Example 15A is a method for a service producer to provide performancemanagement (PM) service for a network slice, the method comprising:receiving a request, from an authorized consumer, to create a networkslice instance (NSI) measurement job to collect performance data of oneor more NSI, wherein the request indicates whether the performance datais to be reported by performance data file or by performance datastreaming; decomposing the performance data of the one or more NSI intoperformance data types of constituent network slice subnet instances(NSSIs) and/or constituent network functions (NFs); and creating a newmeasurement job for at least one of the constituent NSSI(s) or theconstituent NF(s).

Example 16A is the method of Example 15A, wherein creating the newmeasurement job comprises: determining whether decomposed performancedata of the constituent NSSI(s) can be collected by existing measurementjob(s) for NSSI(s); and in response to determining that the decomposedperformance data of the constituent NSSI(s) cannot be collected by theexisting measurement job(s) for NSSI(s), creating the new measurementjob for the constituent NSSI(s).

Example 17A is the method of Example 15A, wherein creating the newmeasurement job comprises: determining whether decomposed performancedata of the constituent NF(s) can be collected by existing measurementjob(s) for NF(s); and in response to determining that the decomposedperformance data of the constituent NF(s) cannot be collected by theexisting measurement job(s) for NF(s), requesting an NF PM serviceproducer to create the new measurement job for the constituent NF(s).

Example 18A is the method of Example 15A, wherein receiving the requestcomprises receiving an NSI measurement job creation request from theauthorized consumer.

Example 19A is the method of Example 15A, wherein the service producercomprises a network slice management function (NSMF).

Example 20A is the method of Example 15A, wherein the service producercomprises an NSI measurement job control service producer.

Example 21A is the method of Example 15A, further comprising: receivinga query, from the authorized consumer, to report information about oneor more ongoing NSI measurement job corresponding to the authorizedconsumer; and in response to the query, providing the information aboutthe one or more ongoing NSI measurement job to the authorized consumer.

Example 22A is the method of Example 15A, further comprising: if therequest to create the NSI measurement job indicates that the performancedata is to be reported by the performance data file, sending aperformance data file ready notification to the authorized consumer; andif the request to create the NSI measurement job indicates that theperformance data is to be reported by the performance data streaming,sending a performance data stream to the authorized consumer. In certainembodiments, the method of Example 15A may be performed by a firstapparatus and the method of Example 22A may be performed by a secondapparatus.

Example 23A is a method to create a measurement job for collectingnetwork or sub-network performance data that are not specific to networkslicing, the method comprising: receiving a request, from an authorizedconsumer, to create a measurement job for collecting non-slice-specificnetwork performance data, wherein the request indicates whether theperformance data is to be reported by performance data file or byperformance data streaming; decomposing non-slice-specific networkperformance data into performance data types of constituent networkfunctions (NFs); determining whether the performance data types of theconstituent NF(s) can be collected by existing measurement jobs forNF(s); and requesting to create one or more new measurement job for theconstituent NF(s).

Example 24A is the method of Example 23A, wherein the method isperformed by a network performance management function (NPMF).

Example 25A is the method of Example 23A, wherein the method isperformed by a network measurement job control service producer, andwherein requesting to create the one or more new measurement job for theconstituent NF(s) comprises requesting an NF measurement job controlservice producer to create the one or more new measurement job.

Example 26A is the method of Example 25A, wherein to create the one ormore new measurement jobs comprises requesting the constituent NF(s) tocollect the performance data.

Example 27A is the method of Example 23A, further comprising: receivinga query, from the authorized consumer, to report information aboutongoing measurement jobs to collect network or sub-network performancedata that are not specific to network slicing; and in response to thequery, providing the information about the ongoing measurement jobs tothe authorized consumer.

Example 28A is the method of Example 23A, further comprising: if therequest to create the measurement job for collecting thenon-slice-specific network performance data indicates that theperformance data is to be reported by the performance data file, sendinga performance data file ready notification to the authorized consumer;and if the request to create a measurement job for collecting thenon-slice-specific network performance data indicates that theperformance data is to be reported by the performance data streaming,sending a performance data stream to the authorized consumer. In certainembodiments, the method of Example 23A may be performed by a firstapparatus and the method of Example 28A may be performed by a secondapparatus.

Example 29A is an apparatus for a service producer in a wireless networkto provide performance management related service for one or morenetwork function (NF), the apparatus comprising: a memory interface tosend or receive, to or from a memory device, a measurement job creationrequest from an authorized consumer; and a processor to: process themeasurement job creation request from the an authorized consumer, themeasurement job creation request to create a measurement job to collectperformance data of the one or more NF; and in response to themeasurement job creation request, generate a request for the one or moreNF to collect the performance data, wherein the measurement job creationrequest indicates whether the performance data is to be reported byperformance data file or by performance data streaming.

Example 30A is a non-transitory computer-readable storage medium, thecomputer-readable storage medium including instructions that whenexecuted by a computer, cause the computer to: receive a measurement jobcreation request, from an authorized consumer, to create a measurementjob to collect performance data of the one or more NF; and in responseto the measurement job creation request, request the one or more NF tocollect the performance data, wherein the measurement job creationrequest indicates whether the performance data is to be reported byperformance data file or by performance data streaming.

Example 31A is an apparatus for a network slice subnet instance (NSSI)measurement job control service, the apparatus comprising: a memoryinterface to send or receive, to or from a memory device, a request tocreate an NSSI measurement job; and a processor to: the request tocreate the NSSI measurement job, the request to collect performance dataof one or more NSSI; decompose the performance data of the one or moreNSSI into performance data types of constituent NSSIs and/or networkfunctions (NFs); determine whether the performance data types of theconstituent NSSI(s) and/or NFs can be collected by existing measurementjobs, if any, for the constituent NSSI(s) and/or NFs; and in response todetermining that the performance data types cannot be collected by theexisting measurement jobs for the constituent NSSI(s) and/or NFs, createone or more new measurement jobs for the constituent NSSI(s) and/or NFs,respectively.

Example 32A is a computing apparatus, the computing apparatus comprisinga processor and a memory storing instructions. The processor and thememory storing instructions that, when executed by the processor,configure the apparatus to: receive a request to create an NSSImeasurement job to collect performance data of one or more NSSI;decompose the performance data of the one or more NSSI into performancedata types of constituent NSSIs and/or network functions (NFs);determine whether the performance data types of the constituent NSSI(s)and/or NFs can be collected by existing measurement jobs, if any, forthe constituent NSSI(s) and/or NFs: and in response to determining thatthe performance data types cannot be collected by the existingmeasurement jobs for the constituent NSSI(s) and/or NFs, create one ormore new measurement jobs for the constituent NSSI(s) and/or NFs,respectively.

Example 33A is an apparatus for a service producer to provideperformance management (PM) service for a network slice, the computingapparatus comprising a memory interface and a processor. The memoryinterface to send or receive, to or from a memory device, a request froman authorized consumer to create a network slice instance (NSI)measurement job. The processor to: process the request, from theauthorized consumer, the request to create a network slice instance(NSI) measurement job to collect performance data of one or more NSI,wherein the request indicates whether the performance data is to bereported by performance data file or by performance data streaming;decompose the performance data of the one or more NSI into performancedata types of constituent network slice subnet instances (NSSIs) and/orconstituent network functions (NFs); and create a new measurement jobfor at least one of the constituent NSSI(s) or the constituent NF(s).

Example 34A is a computing apparatus, the computing apparatus comprisinga processor and a memory storing instructions. The processor and thememory storing instructions that, when executed by the processor,configure the apparatus to: receive a request, from an authorizedconsumer, to create a network slice instance (NSI) measurement job tocollect performance data of one or more NSI, wherein the requestindicates whether the performance data is to be reported by performancedata file or by performance data streaming; decompose the performancedata of the one or more NSI into performance data types of constituentnetwork slice subnet instances (NSSIs) and/or constituent networkfunctions (NFs); and create a new measurement job for at least one ofthe constituent NSSI(s) or the constituent NF(s).

Example 35A is an apparatus to create a measurement job for collectingnetwork or sub-network performance data that are not specific to networkslicing, the apparatus comprising a memory interface and a processor.The memory interface to send or receive, to or from a memory device, arequest from an authorized consumer to create a measurement job. Theprocessor to: process the request, from the authorized consumer, therequest to create a measurement job for collecting non-slice-specificnetwork performance data, wherein the request indicates whether theperformance data is to be reported by performance data file or byperformance data streaming; decompose non-slice-specific networkperformance data into performance data types of constituent networkfunctions (NFs); determine whether the performance data types of theconstituent NF(s) can be collected by existing measurement jobs forNF(s); and request to create one or more new measurement job for theconstituent NF(s).

Example 36A is a computing apparatus, the computing apparatus comprisinga processor and a memory storing instructions. The processor and thememory storing instructions that, when executed by the processor,configure the apparatus to: receive a request, from an authorizedconsumer, to create a measurement job for collecting non-slice-specificnetwork performance data, wherein the request indicates whether theperformance data is to be reported by performance data file or byperformance data streaming; decompose non-slice-specific networkperformance data into performance data types of constituent networkfunctions (NFs); determine whether the performance data types of theconstituent NF(s) can be collected by existing measurement jobs forNF(s); and request to create one or more new measurement job for theconstituent NF(s).

Example 37A is a computing apparatus including a processor and a memorystoring instructions that, when executed by the processor, configure theapparatus to perform the method of any of Examples 1A-28A.

Example 38A is a non-transitory computer-readable storage mediumincluding instructions that, when processed by a computer, configure thecomputer to perform the method of any of Examples 1A-28A.

Example 39A is an apparatus comprising means to perform the method ofany of Examples 1A-28A.

Example 1B may include a service producer to provide PerformanceManagement (PM) service for NF, the service producer configured to:receive a request for creating measurement job for NF from an authorizedconsumer; create the measurement job on the NF; and respond themeasurement job creation request to the authorized consumer.

Example 2B may include the subject matter of Example 1B or some otherexample herein, wherein the service producer is NF PM Function (NFPMF)or NF.

Example 3B may include the subject matter of Examples 1B and 2B or someother example herein, wherein creating the measurement job on the NFincludes sending the measurement job creation request to NF, in case theservice producer is not NF.

Example 4B may include the subject matter of Examples 1B to 3B or someother example herein, wherein the measurement job is to collect theperformance data of NF.

Example 5B may include the subject matter of Examples 1B to 4B or someother example herein, wherein the NF reports the performance data of NFto a data repository.

Example 6B may include a data repository to provide the NF performancedata service, the data repository configured to: get the performancedata of NF; store the performance data of NF; and/or report theperformance data of NF to the authorized consumer.

Example 7B may include the subject matter of Example 6B or some otherexample herein, wherein the service producer is NF performance datarepository (NFPDR).

Example 8B may include a service producer to provide PerformanceManagement (PM) service for Network Slice SubNet, the service producerconfigured to: receive a request for creating measurement job forNetwork Slice SubNet Instance (NSSI) from an authorized consumer;decompose the performance data of NSSI to performance data of NF(s);check whether the decomposed performance data of NF(s) can be collectedby the existing measurement job(s) for NF(s); request to createmeasurement job(s) for NF(s) via the service producer providing the PMservice for NFs (as described in Example 1B to 5B), if needed; receiveresponse for the request of creating measurement job(s) for NF(s);respond the request of creating measurement job for NSSI to theauthorized consumer; get the performance data of NF(s) from the datarepository of Examples 6B and 7B and/or some other examples herein;store the performance data of NFs; generate the performance data for theNSSI based on the performance data of NF(s); and report the performancedata of the NSSI to a data repository storing the performance data ofNSSIs. Example 9B may include the subject matter of example 8 or someother example herein, wherein the service producer providing PerformanceManagement (PM) service for Network Slice SubNet is NSSMF (Network SliceSubNet Management Function).

Example 10B may include a service producer to provide PerformanceManagement (PM) service for Network Slice, by: receive a request forcreating measurement job for Network Slice Instance (NSI) from anauthorized consumer; decompose the performance data of NSI toperformance data of NSSI(s); check whether the decomposed performancedata of NSSI(s) can be collected by the existing measurement job(s) forNSSI(s); request to create measurement job(s) for NSSI(s) via theservice producer providing the PM service for Network Slice SubNet (asdescribed in Examples 8B to 9B), if needed; receive response for therequest of creating measurement job(s) for NSSI(s); and/or decompose theperformance data of NSI to performance data of NF(s); check whether thedecomposed performance data of NF(s) can be collected by the existingmeasurement job(s) for NF(s); request to create measurement job(s) forNF(s) via the service producer providing the PM service for NFs (asdescribed in Example 1B to 5B), if needed; receive response for therequest of creating measurement job(s) for NF(s); respond the request ofcreating measurement job for NSI to the authorized consumer; get theperformance data of NSSI(s) from a data repository storing theperformance data of NSSIs; get the performance data of NF(s) from a datarepository (as described in Example 6B and 7B) storing the performancedata of NFs; generate the performance data for the NSI based on theperformance data of NSSI(s) and/or performance data of NF(s); and reportthe performance data of the NSI to a data repository storing theperformance data of NSIs.

Example 11B may include the subject matter of Example 10B or some otherexample herein, wherein the service producer providing PerformanceManagement (PM) service for Network Slice is NSMF (Network SliceManagement Function).

Example 12B may include a service producer to provide PerformanceManagement (PM) service for non-slice specific network, the serviceproducer configured to: receive a request for creating measurement jobfor a non-slice-specific network from an authorized consumer; decomposethe performance data of non-slice-specific network to performance dataof NF(s); check whether the decomposed performance data of NF can becollected by the existing measurement job(s) for NF(s); request tocreate measurement job(s) for NF(s) via the service producer providingthe PM service for NFs (as described in Example 1B to 5B), if needed;receive response for the request of creating measurement job(s) forNF(s); respond the request of creating measurement job fornon-slice-specific network to the authorized consumer; get theperformance data of NF(s) from a data repository (as described inExample 6B and 7B) storing the performance data of NFs; generate theperformance data for the non-slice-specific network based on theperformance data of NF(s); and report the performance data of thenon-slice-specific network to a data repository storing the performancedata of non-slice-specific networks.

Example 13B may include the subject matter of Example 12B or some otherexample herein, wherein the service producer providing PerformanceManagement (PM) service for non-slice-specific network is NetworkPerformance Management Function (NPMF).

Example 14B may include a data repository to provide a networkperformance data service, the data repository configured to: get theperformance data of network; store the performance data of the network;and/or report the performance data of the network to the authorizedconsumer.

Example 15B may include the subject matter of Example 14B or some otherexample herein, wherein the network is a NSSI, NSI or a non-slicespecific network.

Example 16B may include the subject matter of Examples 14B and 15B orsome other example herein, wherein the data repository is Networkperformance data repository (NWPDR or NPDR).

Example 17B may include the subject matter of Example 1B to Example 16Bor some other example herein, wherein the performance data is periodicalperformance data.

Example 18B may include the subject matter of Example 1B to Example 16Bor some other example herein, wherein the performance data is real-timeperformance data.

Example 19B may include the subject matter of Example 1B to Example 18Bor some other example herein, wherein the measurement job creationrequest indicates the performance data to be collected are periodicalperformance data or real-time performance data.

Example 20B may include the subject matter of Examples 6B, 7B, 14B to16B, and 17B or some other example herein, wherein reporting theperiodical performance data is according to reporting period of themeasurement job.

Example 21B may include the subject matter of examples 6B, 7B, 14B to16B, 17B and 20B or some other example herein, wherein reporting theperiodical performance data is by sending the performance data fileready notification.

Example 22B may include the subject matter of examples 6B, 7B, 14B to16B, and 18B or some other example herein, wherein reporting thereal-time performance data is by performance data streaming.

Example 23B may include the subject matter of Examples 1B to 12B or someother example herein, wherein the performance data of NF is number ofattempted RRC connection establishments.

Example 24B may include the subject matter of Example 23B or some otherexample herein, wherein the number of attempted RRC connectionestablishments is split into subcounters for each establishment causeand/or subcounters for each NSI.

Example 25B may include the subject matter of Example 23B and 24B orsome other example herein, wherein the measurement of number ofattempted RRC connection establishments is triggered on receipt of anRRCConnectionRequest message by the gNB from the UE, and each receivedRRCConnectionRequest message is added to the relevant subcounter for theestablishment cause and/or the relevant subcounter for the NSI.

Example 26B may include the subject matter of Examples 1B to 12B or someother example herein, wherein the performance data of NF is number ofsuccessful RRC connection establishments.

Example 27B may include the subject matter of Example 26B or some otherexample herein, wherein the number of successful RRC connectionestablishments is split into subcounters for each establishment causeand/or subcounters for each NSI.

Example 28B may include the subject matter of Examples 26B and 27B orsome other example herein, wherein the measurement of number ofsuccessful RRC connection establishments is triggered on receipt of anRRCConnectionSetupComplete message by the gNB from the UE, and eachreceived RRCConnectionSetupComplete message is added to the relevantsubcounter for the establishment cause and/or the relevant subcounterfor the NSI.

Example 29B may include the subject matter of Examples 1B to 12B or someother example herein, wherein the performance data of NF is number offailed RRC connection establishments.

Example 30B may include the subject matter of Example 26B or some otherexample herein, wherein the number of failed RRC connectionestablishments is split into subcounters for each failure cause.

Example 31B may include the subject matter of Examples 29B and 30B orsome other example herein, wherein the measurement of number of failedRRC connection establishments is triggered on transmission of anRRCConnectionReject message by the gNB from the UE, and each transmittedRRCConnectionReject message is added to the relevant subcounter for thefailure cause.

Example 32B may include an apparatus comprising means to perform one ormore elements of a method described in or related to any of Examples1B-31B, or any other method or process described herein.

Example 33B may include one or more non-transitory computer-readablemedia comprising instructions to cause an electronic device, uponexecution of the instructions by one or more processors of theelectronic device, to perform one or more elements of a method describedin or related to any of Examples 1B-31B, or any other method or processdescribed herein.

Example 34B may include an apparatus comprising logic, modules, orcircuitry to perform one or more elements of a method described in orrelated to any of Examples 1B-31B, or any other method or processdescribed herein. Example 35B may include a method, technique, orprocess as described in or related to any of Examples 1B-31B, orportions or parts thereof.

Example 36B may include an apparatus comprising: one or more processorsand one or more computer readable media comprising instructions that,when executed by the one or more processors, cause the one or moreprocessors to perform the method, techniques, or process as described inor related to any of Examples 1B-31B, or portions thereof.

Example 37B may include a signal as described in or related to any ofExamples 1B-31B, or portions or parts thereof.

Example 38B may include a signal in a wireless network as shown anddescribed herein. Example 39B may include a method of communicating in awireless network as shown and described herein.

Example 40B may include a system for providing wireless communication asshown and described herein.

Example 41B may include a device for providing wireless communication asshown and described herein.

Any of the above described examples may be combined with any otherexample (or combination of examples), unless explicitly statedotherwise. The foregoing description of one or more implementationsprovides illustration and description, but is not intended to beexhaustive or to limit the scope of embodiments to the precise formdisclosed. Modifications and variations are possible in light of theabove teachings or may be acquired from practice of various embodiments.

Embodiments and implementations of the systems and methods describedherein may include various operations, which may be embodied inmachine-executable instructions to be executed by a computer system. Acomputer system may include one or more general-purpose orspecial-purpose computers (or other electronic devices). The computersystem may include hardware components that include specific logic forperforming the operations or may include a combination of hardware,software, and/or firmware.

Computer systems and the computers in a computer system may be connectedvia a network. Suitable networks for configuration and/or use asdescribed herein include one or more local area networks, wide areanetworks, metropolitan area networks, and/or Internet or IP networks,such as the World Wide Web, a private Internet, a secure Internet, avalue-added network, a virtual private network, an extranet, anintranet, or even stand-alone machines which communicate with othermachines by physical transport of media. In particular, a suitablenetwork may be formed from parts or entireties of two or more othernetworks, including networks using disparate hardware and networkcommunication technologies.

One suitable network includes a server and one or more clients; othersuitable networks may include other combinations of servers, clients,and/or peer-to-peer nodes, and a given computer system may function bothas a client and as a server. Each network includes at least twocomputers or computer systems, such as the server and/or clients. Acomputer system may include a workstation, laptop computer,disconnectable mobile computer, server, mainframe, cluster, so-called“network computer” or “thin client,” tablet, smart phone, personaldigital assistant or other hand-held computing device, “smart” consumerelectronics device or appliance, medical device, or a combinationthereof.

Suitable networks may include communications or networking software,such as the software available from Novell®, Microsoft®, and othervendors, and may operate using TCP/IP, SPX, IPX, and other protocolsover twisted pair, coaxial, or optical fiber cables, telephone lines,radio waves, satellites, microwave relays, modulated AC power lines,physical media transfer, and/or other data transmission “wires” known tothose of skill in the art. The network may encompass smaller networksand/or be connectable to other networks through a gateway or similarmechanism.

Various techniques, or certain aspects or portions thereof, may take theform of program code (i.e., instructions) embodied in tangible media,such as floppy diskettes, CD-ROMs, hard drives, magnetic or opticalcards, solid-state memory devices, a nontransitory computer-readablestorage medium, or any other machine-readable storage medium wherein,when the program code is loaded into and executed by a machine, such asa computer, the machine becomes an apparatus for practicing the varioustechniques. In the case of program code execution on programmablecomputers, the computing device may include a processor, a storagemedium readable by the processor (including volatile and nonvolatilememory and/or storage elements), at least one input device, and at leastone output device. The volatile and nonvolatile memory and/or storageelements may be a RAM, an EPROM, a flash drive, an optical drive, amagnetic hard drive, or other medium for storing electronic data. TheeNB (or other base station) and UE (or other mobile station) may alsoinclude a transceiver component, a counter component, a processingcomponent, and/or a clock component or timer component. One or moreprograms that may implement or utilize the various techniques describedherein may use an application programming interface (API), reusablecontrols, and the like. Such programs may be implemented in a high-levelprocedural or an object-oriented programming language to communicatewith a computer system. However, the program(s) may be implemented inassembly or machine language, if desired. In any case, the language maybe a compiled or interpreted language, and combined with hardwareimplementations.

Each computer system includes one or more processors and/or memory;computer systems may also include various input devices and/or outputdevices. The processor may include a general purpose device, such as anIntel, AMD®, or other “off-the-shelf” microprocessor. The processor mayinclude a special purpose processing device, such as ASIC, SoC, SiP,FPGA, PAL, PLA, FPLA, PLD, or other customized or programmable device.The memory may include static RAM, dynamic RAM, flash memory, one ormore flip-flops, ROM, CD-ROM, DVD, disk, tape, or magnetic, optical, orother computer storage medium. The input device(s) may include akeyboard, mouse, touch screen, light pen, tablet, microphone, sensor, orother hardware with accompanying firmware and/or software. The outputdevice(s) may include a monitor or other display, printer, speech ortext synthesizer, switch, signal line, or other hardware withaccompanying firmware and/or software.

It should be understood that many of the functional units described inthis specification may be implemented as one or more components, whichis a term used to more particularly emphasize their implementationindependence. For example, a component may be implemented as a hardwarecircuit comprising custom very large scale integration (VLSI) circuitsor gate arrays, or off-the-shelf semiconductors such as logic chips,transistors, or other discrete components. A component may also beimplemented in programmable hardware devices such as field programmablegate arrays, programmable array logic, programmable logic devices, orthe like.

Components may also be implemented in software for execution by varioustypes of processors. An identified component of executable code may, forinstance, comprise one or more physical or logical blocks of computerinstructions, which may, for instance, be organized as an object, aprocedure, or a function. Nevertheless, the executables of an identifiedcomponent need not be physically located together, but may comprisedisparate instructions stored in different locations that, when joinedlogically together, comprise the component and achieve the statedpurpose for the component.

Indeed, a component of executable code may be a single instruction, ormany instructions, and may even be distributed over several differentcode segments, among different programs, and across several memorydevices. Similarly, operational data may be identified and illustratedherein within components, and may be embodied in any suitable form andorganized within any suitable type of data structure. The operationaldata may be collected as a single data set, or may be distributed overdifferent locations including over different storage devices, and mayexist, at least partially, merely as electronic signals on a system ornetwork. The components may be passive or active, including agentsoperable to perform desired functions.

Several aspects of the embodiments described will be illustrated assoftware modules or components. As used herein, a software module orcomponent may include any type of computer instruction orcomputer-executable code located within a memory device. A softwaremodule may, for instance, include one or more physical or logical blocksof computer instructions, which may be organized as a routine, program,object, component, data structure, etc., that perform one or more tasksor implement particular data types. It is appreciated that a softwaremodule may be implemented in hardware and/or firmware instead of or inaddition to software. One or more of the functional modules describedherein may be separated into sub-modules and/or combined into a singleor smaller number of modules.

In certain embodiments, a particular software module may includedisparate instructions stored in different locations of a memory device,different memory devices, or different computers, which togetherimplement the described functionality of the module. Indeed, a modulemay include a single instruction or many instructions, and may bedistributed over several different code segments, among differentprograms, and across several memory devices. Some embodiments may bepracticed in a distributed computing environment where tasks areperformed by a remote processing device linked through a communicationsnetwork. In a distributed computing environment, software modules may belocated in local and/or remote memory storage devices. In addition, databeing tied or rendered together in a database record may be resident inthe same memory device, or across several memory devices, and may belinked together in fields of a record in a database across a network.

Reference throughout this specification to “an example” means that aparticular feature, structure, or characteristic described in connectionwith the example is included in at least one embodiment. Thus,appearances of the phrase “in an example” in various places throughoutthis specification are not necessarily all referring to the sameembodiment.

As used herein, a plurality of items, structural elements, compositionalelements, and/or materials may be presented in a common list forconvenience. However, these lists should be construed as though eachmember of the list is individually identified as a separate and uniquemember. Thus, no individual member of such list should be construed as ade facto equivalent of any other member of the same list solely based onits presentation in a common group without indications to the contrary.In addition, various embodiments and examples may be referred to hereinalong with alternatives for the various components thereof. It isunderstood that such embodiments, examples, and alternatives are not tobe construed as de facto equivalents of one another, but are to beconsidered as separate and autonomous representations.

Furthermore, the described features, structures, or characteristics maybe combined in any suitable manner in one or more embodiments. In thefollowing description, numerous specific details are provided, such asexamples of materials, frequencies, sizes, lengths, widths, shapes,etc., to provide a thorough understanding of the embodiments. Oneskilled in the relevant art will recognize, however, that theembodiments may be practiced without one or more of the specificdetails, or with other methods, components, materials, etc. In otherinstances, well-known structures, materials, or operations are not shownor described in detail to avoid obscuring aspects of embodiments.

It should be recognized that the systems described herein includedescriptions of specific embodiments. These embodiments can be combinedinto single systems, partially combined into other systems, split intomultiple systems or divided or combined in other ways. In addition, itis contemplated that parameters/attributes/aspects/etc. of oneembodiment can be used in another embodiment. Theparameters/attributes/aspects/etc. are merely described in one or moreembodiments for clarity, and it is recognized that theparameters/attributes/aspects/etc. can be combined with or substitutedfor parameters/attributes/etc. of another embodiment unless specificallydisclaimed herein.

Although the foregoing has been described in some detail for purposes ofclarity, it will be apparent that certain changes and modifications maybe made without departing from the principles thereof. It should benoted that there are many alternative ways of implementing both theprocesses and apparatuses described herein. Accordingly, the presentembodiments are to be considered illustrative and not restrictive, andthe description is not to be limited to the details given herein, butmay be modified within the scope and equivalents of the appended claims.

1-28. (canceled)
 29. An apparatus of a New Radio radio access node (gNB)in a New Radio network, the apparatus comprising: a Radio Frequency (RF)circuitry interface to send and receive messages to and from a RFcircuitry of the gNB; and one or more processors coupled to the RFcircuitry interface, the processor to: detect Radio Resource Control(RRC) connection establishment attempt messages from a UE; and add eachRRC connection establishment attempt message of the RRC connectionestablishment attempt messages to a relevant per establishment attemptcause measurement, wherein a sum of per establishment attempt causemeasurements is to equal a number of RRC connection establishmentattempt messages, wherein each per establishment attempt causemeasurement is an integer value.
 30. The apparatus of claim 29, the oneor more processors to further: detect RRC SetupComplete messages thatindicate respective successful RRC connection establishments; and addeach RRC SetupComplete message of the RRC SetupComplete messages to arelevant per establishment cause measurement, wherein a sum of perestablishment cause measurements is to equal a number of RRCSetupComplete messages, wherein each per establishment cause measurementis an integer value.
 31. The apparatus of claim 30, the one or moreprocessors to further: encode for transmission to the UE RRC rejectmessages to indicate respective failed connection establishments withthe UE; and add each RRC reject message of the RRC reject messages to arelevant per failure cause measurement, wherein each per failure causemeasurement is an integer value.
 32. The apparatus of claim 31, wherein:each per establishment attempt cause measurement is associated with afirst name having a form “RRC.ConnEstabAtt.Cause”; each perestablishment cause measurement is associated with a second name havinga form “RRC.ConnEstabSucc.Cause”; each per failure cause measurements isassociated with a third name having a form “RRC.ConnEstabFail,” wherethe third name further includes “.Cause”; and “.Cause” is to identify acause for respective ones of said each per establishment attempt causemeasurement, said each per establishment cause measurement; and saideach per failure cause measurements.
 33. The apparatus of claim 31,wherein the one or more processors are to cause the per establishmentattempt cause measurements, the per establishment cause measurements,and the per failure cause measurements to be used for performanceassurance associated with the network.
 34. The apparatus of claim 31,wherein the per establishment attempt cause measurements, the perestablishment cause measurements, and the per failure cause measurementsare valid for packet switched traffic.
 35. The apparatus of claim 29,further including a front end module coupled to the one or moreprocessors.
 36. The apparatus of claim 35, further including one or moreantennas coupled to the front end module, the one or more antennas toreceive the RRC connection establishment attempt messages.
 37. Theapparatus of claim 31, wherein the network includes a 5G System (5GS).38. A system of a New Radio radio access node (gNB) to be used in a NewRadio network, the system including: a radio frequency (RF) circuitryincluding mixer circuitry, amplifier circuitry and filter circuitry; andan apparatus comprising: a RF circuitry interface coupled to the RFcircuitry to send and receive messages to and from the RF circuitry; andone or more processors coupled to the RF circuitry interface, theprocessor to: detect Radio Resource Control (RRC) connectionestablishment attempt messages from a UE; and add each RRC connectionestablishment attempt message of the RRC connection establishmentattempt messages to a relevant per establishment attempt causemeasurement, wherein a sum of per establishment attempt causemeasurements is to equal a number of RRC connection establishmentattempt messages, wherein each per establishment attempt causemeasurement is an integer value.
 39. The system of claim 38, the one ormore processors to further: detect RRC SetupComplete messages thatindicate respective successful RRC connection establishments; and addeach RRC SetupComplete message of the RRC SetupComplete messages to arelevant per establishment cause measurement, wherein a sum of perestablishment cause measurements is to equal a number of RRCSetupComplete messages, wherein each per establishment cause measurementis an integer value.
 40. The system of claim 39, the one or moreprocessors to further: encode for transmission to the UE RRC rejectmessages to indicate respective failed connection establishments withthe UE; and add each RRC reject message of the RRC reject messages to arelevant per failure cause measurement, wherein each per failure causemeasurement is an integer value.
 41. One or more non-transitorycomputer-readable media comprising instructions to cause an apparatus ofa New Radio radio access node (gNB) in a New Radio network, uponexecution of the instructions by one or more processors of theapparatus, to perform operations including: detecting Radio ResourceControl (RRC) connection establishment attempt messages from a UE; andadding each RRC connection establishment attempt message of the RRCconnection establishment attempt messages to a relevant perestablishment attempt cause measurement, wherein a sum of perestablishment attempt cause measurements is to equal a number of RRCconnection establishment attempt messages, wherein each perestablishment attempt cause measurement is an integer value.
 42. Thecomputer-readable media of claim 41, the operations further including:detecting RRC SetupComplete messages that indicate respective successfulRRC connection establishments; and adding each RRC SetupComplete messageof the RRC SetupComplete messages to a relevant per establishment causemeasurement, wherein a sum of per establishment cause measurements is toequal a number of RRC SetupComplete messages, wherein each perestablishment cause measurement is an integer value.
 43. Thecomputer-readable media of claim 42, the operations further including:encoding for transmission to the UE RRC reject messages to indicaterespective failed connection establishments with the UE; and adding eachRRC reject message of the RRC reject messages to a relevant per failurecause measurement, wherein each per failure cause measurement is aninteger value.
 44. The computer-readable media of claim 43, wherein:each per establishment attempt cause measurement is associated with afirst name having a form “RRC.ConnEstabAtt.Cause”; each perestablishment cause measurement is associated with a second name havinga form “RRC.ConnEstabSucc.Cause”; each per failure cause measurements isassociated with a third name having a form “RRC.ConnEstabFail,” wherethe third name further includes “.Cause”; and “.Cause” is to identify acause for respective ones of said each per establishment attempt causemeasurement, said each per establishment cause measurement; and saideach per failure cause measurements.
 45. The computer-readable media ofclaim 43, the operations further including causing the per establishmentattempt cause measurements, the per establishment cause measurements,and the per failure cause measurements to be used for performanceassurance associated with the network.
 46. The computer-readable mediaof claim 43, wherein the per establishment attempt cause measurements,the per establishment cause measurements, and the per failure causemeasurements are valid for packet switched traffic.
 47. Thecomputer-readable media of claim 41, the operations further includingreceiving the RRC connection establishment attempt messages.
 48. Thecomputer-readable media of claim 41, wherein the network includes a 5GSystem (5GS).